Fixed TypeInfo for ClientCursor.#484
Conversation
037dd74 to
5cc1a0b
Compare
TypeInfo had a hardcoded binary=True which doesn't work to well for ClientCursor.
5cc1a0b to
bfde9f0
Compare
|
Hi @dvarrazzo, I hope this PR is correct -- I couldn't find any reference to why Assuming the tests pass and this PR is merge-able, when do you think you could cut a release with it? I am asking because I'd like to figure out if we should patch around this in Django or can just raise the minimum required version of psycopg in time for Django 4.2. |
|
Hey hello! Thank you very much for the MR! The binary was there because all the types involved support binary loaders so it was ok to do that, and going in a general direction of trying to use more binary paths. This predates the introduction of the client cursors, and the combination was missing from the test suite. Thank you very much for adding tests and release notes too! I can merge and make a new release pretty soon, maybe even tonight. |
|
@pauloxnet @apollo13 Psycopg 3.1.8 released! |
|
Wow, much appreciated. Thank you for the rapid turnaround! |
TypeInfo had a hardcoded binary=True which doesn't work to well for ClientCursor.
Without this change we'd get: