| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Special thanks to Hannes Ljungberg for finding multiple implementation
gaps.
Thanks also to Simon Charette, Adam Johnson, and Mariusz Felisiak for
reviews.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Proper escaping of % in string literals used when defining constaints
was attempted (a8b3f96f6) by overriding quote_value of Postgres and
Oracle schema editor. The same approach was used when adding support for
constraints to the MySQL/MariaDB backend (1fc2c70).
Later on it was discovered that this approach was not appropriate and
that a preferable one was to pass params=None when executing the
constraint creation DDL to avoid any form of interpolation in the first
place (42e8cf47).
When the second patch was applied the corrective of the first were not
removed which caused % literals to be unnecessary doubled. This flew
under the radar because the existings test were crafted in a way that
consecutive %% didn't catch regressions.
This commit introduces an extra test for __exact lookups which
highlights more adequately % doubling problems but also adjust a
previous __endswith test to cover % doubling problems (%\% -> %%\%%).
Thanks Thomas Kolar for the report.
Refs #32369, #30408, #30593.
|
| |
|
|
|
|
|
|
|
|
|
| |
Oracle.
Regression in 09ffc5c1212d4ced58b708cbbf3dfbfb77b782ca.
Thanks Michael Smith for the report.
This also reverts commit 1e4da439556cdd69eb9f91e07f99cf77997e70d2.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QuerySet.update_or_create() with MyISAM storage engine.
QuerySet.update_or_create() uses nested atomic to handle possible
integrity errors taking savepoints as way to mark back the connection
as usable. Savepoints are not returned when
uses_savepoints/can_release_savepoints feature flags are set to False.
As a consequence, QuerySet.update_or_create() assumed the outer atomic
block is tainted and raised TransactionManagementError.
This commit partly reverts 331a460f8f2e4f447b68fba491464b68c9b21fd1.
Thanks gatello-s for the report.
|
|
|
|
| |
self-referential subqueries if supported.
|
|
|
|
| |
when db_collation is set in related field.
|
|
|
|
| |
relation on PostgreSQL.
|
|
|
|
|
|
| |
existing database connection on PostgreSQL.
Regression in 09ffc5c1212d4ced58b708cbbf3dfbfb77b782ca.
|
|
|
| |
Regression in 6a2165816394ab4bb259f6171e82417e098e97a6.
|
|
|
|
|
|
| |
PostgreSQL.
Regression in 09ffc5c1212d4ced58b708cbbf3dfbfb77b782ca.
|
|
|
|
|
| |
hiding clause-less exceptions.
Regression in 3cafb783f3f711c7413ba2b8d7c8ff750bd4d6e1.
|
|
|
|
| |
annotations.
|
| |
|
|
|
|
|
| |
This also fixes test_rename_field_with_check_to_truncated_name() on
MariaDB 10.5.2+ as ALTER TABLE ... RENAME COLUMN statement doesn't
rename inline constraints.
|
|
|
|
|
|
|
|
| |
CheckConstraint if not supported.
The new logic mirrors the logic in SchemaEditor._delete_check_sql()
added in 68ef274bc505cd44f305c03cbf84cf08826200a8.
Thanks Tim Graham for the report.
|
|
|
| |
This was fixed in MySQL 8.0.31.
|
|
|
|
| |
columns names.
|
| |
|
|
|
|
|
|
|
|
| |
Black 23.1.0 is released which, as the first release of the year,
introduces the 2023 stable style. This incorporates most of last year's
preview style.
https://github.com/psf/black/releases/tag/23.1.0
|
|
|
|
|
| |
foreign key index when unique constraint is ignored.
Regression in b731e8841558ee4caaba766c83f34ea9c7004f8b.
|
|
|
|
|
| |
PostgreSQL when server-side binding cursors are used.
Thanks Tim Graham for the review.
|
|
|
| |
isocalendar() returns a namedtuple() instead of tuple in Python 3.9+
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
with psycopg version 3.
Thanks Guillaume Andreu Sabater for the report.
Co-authored-by: Florian Apolloner <apollo13@users.noreply.github.com>
|
| |
|
|
|
|
|
|
|
| |
obj_description(object oid) without a catalog name is deprecated since
there is no guarantee that OIDs are unique across different system
catalogs.
Thanks Tim Graham for the report.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Regression in b7b28c7c189615543218e81319473888bc46d831.
Refs #31377.
Thanks Shai Berger for the report and reviews.
test_aggregation_subquery_annotation_values_collision() has been
updated as queries that are explicitly grouped by a subquery should
always be grouped by it and not its outer columns even if its alias
collides with referenced table columns. This was not possible to
accomplish at the time 10866a10 landed because we didn't have compiler
level handling of colliding aliases.
|
|
|
| |
mysqlclient 1.4.3 is the first release to support Python 3.8.
|
| |
|
|
|
|
| |
Co-authored-by: Mariusz Felisiak <felisiak.mariusz@gmail.com>
|
|
|
|
|
|
|
|
| |
Thanks Jared Chung, Tom Carrick, David Smith, Nick Pope, and Mariusz
Felisiak for reviews.
Co-authored-by: Mariusz Felisiak <felisiak.mariusz@gmail.com>
Co-authored-by: Nick Pope <nick@nickpope.me.uk>
|
|
|
|
| |
MySQL < 8.0.16.
|
|
|
|
|
|
|
| |
This moves setting a database collation to the column type alteration
as both must be set at the same time.
This should also avoid another layer of the column type alteration when
adding database comments support (#18468).
|
|
|
|
|
|
|
| |
Thanks Simon Charette, Tim Graham, and Adam Johnson for reviews.
Co-authored-by: Florian Apolloner <florian@apolloner.eu>
Co-authored-by: Mariusz Felisiak <felisiak.mariusz@gmail.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
internal_size is size for fixed-size types not for char types.
|
| |
|
|
|
|
|
|
|
|
|
| |
- Used connection.info instead of connection.get_parameter_status() and
connection.server_info which don't exist in psycopg 3.
- Set encoding using the client_encoding connection parameter instead
of connection.set_client_encoding() that doesn't exist in psycopg 3.
- Used the dbname connection parameter instead of deprecated
alias - database.
|
|
|
|
| |
MySQL.
|
| |
|
|
|
|
|
|
| |
in-memory SQLite database.
multiprocessing's start method is checked only for in-memory SQLite
databases.
|
| |
|
|
|
|
| |
AssertNumQueriesUponConnectionTests tests.
|
|
|
|
|
|
| |
LiveServerTestCase with in-memory SQLite database.
Thanks Chris Jerdonek for the implementation idea.
|