| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
properties.
|
|
|
|
a related set.
|
|
|
|
Per deprecation timeline.
|
|
Per deprecation timeline.
|
|
Per deprecation timeline.
|
|
Per deprecation timeline.
|
|
timeline.
|
|
|
|
|
|
Also removed support for passing a 3-tuple to include() and support for
setting an instance namespace without an application namespace.
Thanks Marten Kenbeek for completing the patch.
|
|
Per deprecation timeline.
|
|
Per deprecation timeline.
|
|
Per deprecation timeline.
|
|
|
|
|
|
|
|
of the ORM.
Per deprecation timeline.
|
|
|
|
Per deprecation timeline.
|
|
|
|
Per deprecation timeline.
|
|
|
|
|
|
BaseDatabaseOperations.check_aggregate_support().
|
|
Per deprecation timeline.
|
|
|
|
MySQL.
|
|
|
|
operations.
|
|
|
|
|
|
|
|
Thanks Travis Newport for the tests and Josh Smeaton for contributing
to the patch.
|
|
|
|
|
|
|
|
|
|
Thanks Tim Graham and Markus Holtermann for review.
|
|
Thanks Josh Smeaton for Oracle fixes.
|
|
Thanks Mariusz Felisiak for review and Oracle assistance.
Thanks Tim Graham for review and writing docs.
|
|
When an error occurred during the cursor.execute statement, the cursor
is closed. This operation did not fail with client-side cursors. Now,
with server-side cursors, the close operation might fail (example
below). The original error should be raised, not the one raised by
cursor.close(), this is only clean-up code.
For example, one can attempt to create a named cursor for an invalid
query. psycopg will raise an error about the invalid query and the
server-side cursor will not be created on PostgreSQL. When the code
attempts to cursor.close(), it asks psycopg to close a cursor that was
not created. pyscopg raises a new error: psycopg2.OperationalError:
cursor "_django_curs_140365867840512_20" does not exist.
|