| 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.
|
|
|
|
| |
self-referential subqueries if supported.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
No core backend require the feature anymore as it was only added to
support a MySQL'ism that has been deprecated since then.
|
|
|
|
|
|
|
| |
This ensures explicit grouping from using values() before annotating an
aggregate function groups by selected aliases if supported.
The GROUP BY feature is disabled on Oracle because it doesn't support it.
|
|
|
|
|
|
|
|
|
|
|
| |
MySQL.
Columns of the left outer most select statement in a combined query
can be referenced by alias just like by index.
This removes combined query ordering by column index and avoids an
unnecessary usage of RawSQL which causes issues for backends that
specialize the treatment of null ordering.
|
|
|
|
|
|
| |
Bug in 667105877e6723c6985399803a364848891513cc.
Thanks James Beith for the report.
|
| |
|
| |
|
|
|
| |
Always True since 6723a26e59b0b5429a0c5873941e01a2e1bdbb81.
|
| |
|
|
|
|
| |
Thanks Tim Graham for the review.
|
| |
|
|
|
|
|
| |
Thanks Florian Apolloner, Chris Jerdonek, Hannes Ljungberg, Nick Pope,
and Mariusz Felisiak for reviews.
|
|
|
|
| |
DatabaseFeatures.supports_mixed_date_datetime_comparisons.
|
|
|
|
| |
BaseDatabaseFeatures.has_case_insensitive_like to False.
|
| |
|
|
|
|
| |
Co-Authored-By: Simon Charette <charette.s@gmail.com>
|
|
|
|
| |
DatabaseFeatures.supports_expression_indexes to True.
|
|
|
|
|
|
| |
Thanks Simon Charette, Mads Jensen, and Mariusz Felisiak for reviews.
Co-authored-by: Markus Holtermann <info@markusholtermann.eu>
|
|
|
|
| |
set().
|
|
|
|
|
| |
failures.
Co-authored-by: Tim Graham <timograham@gmail.com>
|
| |
|
| |
|
| |
|
|
|
|
| |
Thanks Simon Charette and Mariusz Felisiak for reviews.
|
|
|
|
| |
Previously, backends used different keys "swedish-ci" or "swedish_ci".
|
|
|
|
| |
Thanks Simon Charette for reviews.
|
|
|
|
|
| |
DatabaseFeatures.json_key_contains_list_matching_requires_list.
CockroachDB's behavior matches PostgreSQL.
|
|
|
|
|
|
|
|
|
|
| |
lookups on SQLite.
The current implementation works only for basic examples without
supporting nested structures and doesn't follow "the general principle
that the contained object must match the containing object as to
structure and data contents, possibly after discarding some
non-matching array elements or object key/value pairs from the
containing object".
|
|
|
|
| |
NO_AUTO_VALUE_ON_ZERO SQL mode is enabled.
|
|
|
| |
Bug was fixed in mysqlclient 1.3.13.
|
| |
|
|
|
|
|
|
|
| |
DatabaseFeatures.introspected_field_types.
CockroachDB introspects CharField as TextField and IntegerField as
BigIntegerField.
|
| |
|
|
|
|
| |
DatabaseFeatures.introspected_field_types.
|
|
|
|
| |
QuerySet.select_for_update() on PostgreSQL.
|
|
|
| |
CockroachDB also has them.
|
|
|
|
|
|
|
|
| |
Exists() annotation and aggregation on Oracle.
Oracle requires the EXISTS expression to be wrapped in a CASE WHEN in
the GROUP BY clause.
Regression in efa1908f662c19038a944129c81462485c4a9fe8.
|
|
|
|
|
|
|
|
|
|
|
| |
Thanks to Adam Johnson, Carlton Gibson, Mariusz Felisiak, and Raphael
Michel for mentoring this Google Summer of Code 2019 project and
everyone else who helped with the patch.
Special thanks to Mads Jensen, Nick Pope, and Simon Charette for
extensive reviews.
Co-authored-by: Mariusz Felisiak <felisiak.mariusz@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
Both backends order NULLs first on ascending ordering and last on
descending ordering which makes ORDER BY IS (NOT)? NULL wasteful when
asc(nulls_first) and desc(nulls_last) are used since it prevents indice
usage.
|
| |
|
|
|
|
| |
together with PRECEDING and FOLLOWING".
|
|
|
|
|
|
|
| |
MySQL & MariaDB support the standard IS NULL and IS NOT NULL so
the same workaround used for NULLS FIRST and NULLS LAST that is
used for SQLite < 3.30.0 can be used.
Thanks Simon Charette for the discussion.
|
|
|
|
|
|
| |
DatabaseFeatures.can_return_multiple_columns_from_insert.
Unnecessary since b31e63879eb5d9717e9f890401f7222e4f00c910.
|
|
|
|
| |
DatabaseFeatures.allows_group_by_selected_pks_on_model() to allow enabling optimization for unmanaged models.
|