#29377: DatabaseSchemaEditor: add a hook to run DML statements after the entire
schema is created
-------------------------------------+-------------------------------------
     Reporter:  Maximiliano Robaina  |                    Owner:  nobody
         Type:  New feature          |                   Status:  new
    Component:  Migrations           |                  Version:  2.0
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Maximiliano Robaina):

 * cc: Maximiliano Robaina (added)


Old description:

> This feature request is to better support  of third-party database
> backends.
> In my case (Firebird SQL) to add a new field on already existing and
> populated table is not enough set and drop a default value, we need to
> update the new field with efective default value. It is not possible
> without commit the schema alteration.
> An aproach could be to have a kind of hook to run sql statements (DML
> statement in this case) when the schema  altereation finished (and
> commited). Of course, must bu runned in another transaction.

New description:

 A nice option would be to have a hook to run DML statements after all
 migrations were applied and commited.

 A uses case  (for example in Firebird SQL) is to add a new field on
 already existing and populated table. Is not enough set and drop a default
 value, we need to update the new field with efective default value. It is
 not possible without commit the schema alteration.
 An aproach could be to have a kind of hook to run sql statements (DML
 statement in this case) when the schema  altereation finished (and
 commited). Of course, must bu runned in another transaction.

 This feature request is to better support of third-party database
 backends.

--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.da96fa601c94dccbad061c72dcbb2193%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to