Just committed a change to the update() method in the classic module that fixes a small backward compatibility/usability issue in the current version 5.0: In the case that both an OID and a primary key is provided in a row dictionary, the OID now takes precedence again when looking up the row, as it did in 4.x. It had been changed in 5.0 in the course of demotion of OIDs in general (as Postgres doesn't use them by default any more), but actually this behavior was quite useful, since it allowed updating the primary key of the row very easily together with the other values. I used that feature in a legacy application, and maybe others are also relying on it. I have also added a regression test. Let me know what you think.

http://trac.vex.net:8000/pgtracker/changeset/872

-- Christoph

_______________________________________________
PyGreSQL mailing list
[email protected]
https://mail.vex.net/mailman/listinfo.cgi/pygresql

Reply via email to