<feed xmlns='http://www.w3.org/2005/Atom'>
<title>django.git/django/db/backends/sqlite3/features.py, branch main</title>
<subtitle>django
</subtitle>
<id>http://cgit.adnoto.dev/django.git/atom?h=main</id>
<link rel='self' href='http://cgit.adnoto.dev/django.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/'/>
<updated>2025-12-23T01:33:13Z</updated>
<entry>
<title>Fixed #36818 -- Ensured SQLite connection before accessing max_query_params.</title>
<updated>2025-12-23T01:33:13Z</updated>
<author>
<name>guro-Ishiguro</name>
<email>guro120411@gmail.com</email>
</author>
<published>2025-12-22T15:30:05Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=84bae9c22a8ae7663c56cce5e0c611ea7c17fce1'/>
<id>urn:sha1:84bae9c22a8ae7663c56cce5e0c611ea7c17fce1</id>
<content type='text'>
Regression in 358fd21c47cdf7bda520ce73c5cfd82bba57827b.
</content>
</entry>
<entry>
<title>Fixed #36735 -- Added UUID4 and UUID7 database functions.</title>
<updated>2025-12-12T16:17:08Z</updated>
<author>
<name>Lily Acorn</name>
<email>code@lilyf.org</email>
</author>
<published>2025-11-15T16:29:12Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=accceec9493d08e19d59fa1a59f69c0fdf23bb13'/>
<id>urn:sha1:accceec9493d08e19d59fa1a59f69c0fdf23bb13</id>
<content type='text'>
Co-authored-by: Mariusz Felisiak &lt;felisiak.mariusz@gmail.com&gt;
</content>
</entry>
<entry>
<title>Fixed #24920 -- Added support for DecimalField with no precision.</title>
<updated>2025-11-17T12:43:47Z</updated>
<author>
<name>Mariusz Felisiak</name>
<email>felisiak.mariusz@gmail.com</email>
</author>
<published>2025-11-17T12:43:47Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=1ce6e78dd4beed702f15fa0be798dd17a15d4ba8'/>
<id>urn:sha1:1ce6e78dd4beed702f15fa0be798dd17a15d4ba8</id>
<content type='text'>
Thanks Lily for the review.</content>
</entry>
<entry>
<title>Fixed #36671 -- Dropped support for SQLite &lt; 3.37.</title>
<updated>2025-10-18T19:04:11Z</updated>
<author>
<name>Mariusz Felisiak</name>
<email>felisiak.mariusz@gmail.com</email>
</author>
<published>2025-10-18T19:04:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=d506e4a52847ed4fb80754175d76b6b83ff90929'/>
<id>urn:sha1:d506e4a52847ed4fb80754175d76b6b83ff90929</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Refs #27222 -- Refreshed GeneratedFields values on save() initiated update.</title>
<updated>2025-09-13T22:27:49Z</updated>
<author>
<name>Simon Charette</name>
<email>charette.s@gmail.com</email>
</author>
<published>2025-03-19T05:11:34Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=55a0073b3beb9de8f7c1f7c44a7d0bc10126c841'/>
<id>urn:sha1:55a0073b3beb9de8f7c1f7c44a7d0bc10126c841</id>
<content type='text'>
This required implementing UPDATE RETURNING machinery that heavily
borrows from the INSERT one.
</content>
</entry>
<entry>
<title>Fixed #34262 -- Added support for AnyValue for SQLite, MySQL, Oracle, and Postgresql 16+.</title>
<updated>2025-05-20T08:01:42Z</updated>
<author>
<name>ontowhee</name>
<email>82607723+ontowhee@users.noreply.github.com</email>
</author>
<published>2025-03-16T02:23:28Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=ddb85294159185c5bd5cae34c9ef735ff8409bfe'/>
<id>urn:sha1:ddb85294159185c5bd5cae34c9ef735ff8409bfe</id>
<content type='text'>
Thanks Simon Charette for the guidance and review. Thanks Tim Schilling for the
documentation review. Thanks David Wobrock for investigation and solution proposals.
</content>
</entry>
<entry>
<title>Fixed #36143 -- Made max_query_params respect SQLITE_LIMIT_VARIABLE_NUMBER.</title>
<updated>2025-05-08T10:37:11Z</updated>
<author>
<name>Sage Abdullah</name>
<email>me@laymonage.com</email>
</author>
<published>2025-05-08T07:10:44Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=358fd21c47cdf7bda520ce73c5cfd82bba57827b'/>
<id>urn:sha1:358fd21c47cdf7bda520ce73c5cfd82bba57827b</id>
<content type='text'>
Co-authored-by: Xavier Frankline &lt;xf.xavierfrank@gmail.com&gt;
</content>
</entry>
<entry>
<title>Refs #36052, #32234 -- Removed create_test_table_with_composite_primary_key flag in favor of using CompositePrimaryKey.</title>
<updated>2025-04-30T13:51:48Z</updated>
<author>
<name>Simon Charette</name>
<email>charette.s@gmail.com</email>
</author>
<published>2025-04-29T02:46:13Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=4c75858135589f3a00e32eb4d476074536371a32'/>
<id>urn:sha1:4c75858135589f3a00e32eb4d476074536371a32</id>
<content type='text'>
Now that Django properly supports creating models with composite primary
keys, the tests should use a `CompositePrimaryKey` field instead of a
feature flag to inline backend specific SQL for creating a composite PK.

Specifcially, the inspectdb's test_composite_primary_key was adjusted to
use schema editor instead of per-backend raw SQL.
</content>
</entry>
<entry>
<title>Fixed #35444 -- Added generic support for Aggregate.order_by.</title>
<updated>2025-03-03T10:37:00Z</updated>
<author>
<name>Chris Muthig</name>
<email>camuthig@gmail.com</email>
</author>
<published>2024-12-22T15:30:55Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=4b977a5d7283e7ca51288cc0ed0860e0004653ca'/>
<id>urn:sha1:4b977a5d7283e7ca51288cc0ed0860e0004653ca</id>
<content type='text'>
This moves the behaviors of `order_by` used in Postgres aggregates into
the `Aggregate` class. This allows for creating aggregate functions that
support this behavior across all database engines. This is shown by
moving the `StringAgg` class into the shared `aggregates` module and
adding support for all databases. The Postgres `StringAgg` class is now
a thin wrapper on the new shared `StringAgg` class.

Thank you Simon Charette for the review.
</content>
</entry>
<entry>
<title>Fixed #36148 -- Enabled native tuple comparison lookups on SQLite 3.37+ and Oracle 23.4+.</title>
<updated>2025-02-09T16:45:16Z</updated>
<author>
<name>Simon Charette</name>
<email>charette.s@gmail.com</email>
</author>
<published>2025-01-28T20:04:14Z</published>
<link rel='alternate' type='text/html' href='http://cgit.adnoto.dev/django.git/commit/?id=4a3ad9eebbc16ce80b348644b557c84ecc741be7'/>
<id>urn:sha1:4a3ad9eebbc16ce80b348644b557c84ecc741be7</id>
<content type='text'>
VALUES must be explicitly specified when declaring a sequence of tuples
on SQLite &lt; 3.37 but it's not required on &gt;= 3.37.

See sqlite/sqlite@9289f51 which addressed the last remaining issue with
IN.
</content>
</entry>
</feed>
