Re: [Django] #10236: Change order of actions in syncdb

[Django]

#10236: Change order of actions in syncdb
-------------------------------------+-------------------------------------
Reporter: jbergstroem | Owner: nobody
Type: New feature | Status: new
Component: Core (Management | Version: master
commands) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: order syncdb sql | Needs documentation: 0
index | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):

* stage: Design decision needed => Accepted

Comment:

The discussion on django-developers was in favor of improving the
situation.

--
Ticket URL: <https://code.djangoproject.com/ticket/10236#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#10236: Change order of actions in syncdb
-------------------------------------+-------------------------------------
Reporter: jbergstroem | Owner: nobody
Type: New feature | Status: new
Component: Core (Management | Version: master
commands) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: order syncdb sql | Needs documentation: 0

index | Patch needs improvement: 1

Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------

Changes (by timo):

* needs_better_patch: 0 => 1

--
Ticket URL: <https://code.djangoproject.com/ticket/10236#comment:11>

[Django]

#10236: Change order of actions in syncdb
-------------------------------------+-------------------------------------
Reporter: jbergstroem | Owner: nobody

Type: New feature | Status: closed

Component: Core (Management | Version: master

commands) | Resolution: fixed

Severity: Normal | Triage Stage: Accepted
Keywords: order syncdb sql | Needs documentation: 0
index | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------

Changes (by aaugustin):

* status: new => closed
* resolution: => fixed

Comment:

The original use case was to "remove these indexes that Django created for
me but never are used".

The new migrations framework provide excellent tools to do this, with its
RunSQL operation.

It can be positioned where needed by declaring dependencies.

--
Ticket URL: <https://code.djangoproject.com/ticket/10236#comment:12>