implement pre-result fetcher to support postgres server side cursors
evaluate this patch for implementing a delayed metadata ResultProxy.
Comments (3)
-
reporter -
reporter OK good news and bad news. both is that I have to do
#496to really do this correctly. the server side cursor is only appropriate in the case of a "SELECT". so at this point ExecutionContext, which gives dialects a lot more insight into the current state of a single execution, should be beefed up so dialects can see whats being executed, if its a SELECT or whatever else, make decisions about the cursor and other things etc. -
reporter - changed status to resolved
Ok we went a slightly different route with the result set in that its buffering a single row immediately, in order to have the description immediately available..then it buffers bigger numbers of rows as it gets called again. the whole fix is merged in changeset:2487 and the entire test suite can be run with
--dburi postgres://something --serverside
to test...and all tests pass. - Log in to comment