(#198) - update_after should actually update after

It seems there was a bug where update_after wouldn't
actually cause the query to return immediately, and
instead would still force the user to wait for the
results to be built up.  This fixes that.
This test was failing before my `process.nextTick` fix.