| Age | Commit message (Collapse) | Author |
|
Unused (always True) since its introduction in 132605d889db8767a40243259066b8450428714c.
|
|
PostgreSQL.
The sql_flush() positional argument sequences is replaced by the boolean
keyword-only argument reset_sequences. This ensures that the old
function signature can't be used by mistake when upgrading Django. When
the new argument is True, the sequences of the truncated tables will
reset. Using a single boolean value, rather than a list, allows making a
binary yes/no choice as to whether to reset all sequences rather than a
working on a completely different set.
|
|
|
|
|
|
|
|
Thanks Markus for your contribution and Tim for your review.
|
|
Kept support for creating models without migrations when running tests
(especially for Django's test suite).
|
|
|
|
|
|
|
|
|
|
comprehension
|
|
`io.open` is required on Python 2.7. Just `open` would work on Python 3.
|
|
Thanks rodolfo_3 for the report and the initial patch, and
Josh Smeaton, Shai Berger and Tim Graham for the reviews.
|
|
refs #23395.
|
|
Thanks to Trac alias flakfizer for the report.
|
|
|
|
|
|
This reverts commit cb9c9a7b5879671053c7d2ad6e79943a8814b274.
|
|
|
|
|
|
|
|
|
|
Avoided introducing a new regex-based SQL splitter in the migrations
framework, before we're bound by backwards compatibility.
Adapted this change to the legacy "initial SQL data" feature, even
though it's already deprecated, in order to facilitate the transition
to migrations.
sqlparse becomes mandatory for RunSQL on some databases (all but
PostgreSQL). There's no API to provide a single statement and tell
Django not to attempt splitting. Since we have a more robust splitting
implementation, that seems like a good tradeoff. It's easier to add a
new keyword argument later if necessary than to remove one.
Many people contributed to both tickets, thank you all, and especially
Claude for the review.
Refs #22401.
|
|
in favor of installing sqlparse."
This reverts commit 071c9337750b296d198cced56f3ffad0e176afb6.
This introduced a regression on MySQL and custom SQL is deprecated.
|
|
favor of installing sqlparse.
|
|
Thanks Anssi Kääriäinen for the idea and Simon Charette for the
review.
|
|
This commit touchs various parts of the code base and test framework. Any
found usage of opening a cursor for the sake of initializing a connection
has been replaced with 'ensure_connection()'.
|
|
Universal newlines is enabled by default on py3, and the usage of 'U' is
deprecated in py3.4.
|
|
|
|
Now that the refactorings are complete, it isn't particularly useful any
more, nor very well named. Let's keep the API as simple as possible.
Fixed #21689.
|
|
|
|
|
|
De-aliased pre/post_syncdb to pre/post_migrate to increase
backwards-compatibility.
|
|
Also renamed app_cache to apps and "app cache" to "app registry".
Deprecated AppCache.app_cache_ready() in favor of Apps.ready().
|
|
Reverted 4a56a93cc458e9ab4dcab95d9f5067d4975dd1a2.
|
|
|
|
This commit reverts f44c4a5d0f and 39bbd165.
django.test.simple will be updated in a separate commit as it requires
invasive changes.
|
|
|
|
|
|
Since the original ones in django.db.models.loading were kept only for
backwards compatibility, there's no need to recreate them. However, many
internals of Django still relied on them.
They were also imported in django.db.models. They never appear in the
documentation, except a quick mention of get_models and get_app in the
1.2 release notes to document an edge case in GIS. I don't think that
makes them a public API.
This commit doesn't change the overall amount of global state but
clarifies that it's tied to the app_cache object instead of hiding it
behind half a dozen functions.
|
|
|
|
Thanks Manel Clos for the report and the initial patch, and
Marc Tamlyn and Tim Graham for the review.
|
|
Thanks to berkerpeksag for the report and to claudep
for the review.
|
|
local variables
|
|
|
|
Conflicts:
django/core/management/commands/flush.py
django/core/management/commands/syncdb.py
django/db/models/loading.py
docs/internals/deprecation.txt
docs/ref/django-admin.txt
docs/releases/1.7.txt
|
|
|
|
Thanks al_the_x for the report and fheinz for the draft patch.
|
|
This allows using flush on a subset of the tables without having to
manually cascade to all tables with foreign keys to the tables being
truncated, when they're known to be empty.
On databases where truncate is implemented with DELETE FROM, this
doesn't make a difference. The cascade is allowed, not mandatory.
|