#24362: Migration test failure on Oracle
---------------------------------+-------------------------------------
Reporter: shaib | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.8alpha1
Severity: Release blocker | Resolution: fixed
Keywords: oracle | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+-------------------------------------
Comment (by shaib):
The explanation is that on Oracle, the auto-field is implemented using a
trigger; the code that creates the trigger is added in the `CreateModel`
migration operation as deferred sql. Deferred sql is only executed in the
schema editor's `__exit__`. In most tests around this one in the file you
can see migration operations performed each in its own schema editor. I
did the same here.
--
Ticket URL: <https://code.djangoproject.com/ticket/24362#comment:5>
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/063.a127d8762ccee15e5d89a1a57d8b2b25%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
