#36687: Unexpected IntegrityError and unavailability during Django Oracle
upgrades
involving AutoField/BigAutoField and pre-Django 2.0 legacy triggers
behavior
-------------------------------------+-------------------------------------
Reporter: Fabio Caritas | Owner: (none)
Barrionuevo da Luz |
Type: Uncategorized | Status: closed
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: oracle, oracle 11, | Triage Stage:
ora-00001, AutoField, | Unreviewed
BigAutoField, IntegrityError |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* resolution: => needsinfo
* status: new => closed
Comment:
Hi, thanks for the report.
> The consequence of this is that in some situations, this results in the
creation of a new migration that will, at the database level (Oracle),
change the primary key column type from NUMBER(11) or NUMBER(11) GENERATED
BY DEFAULT ON NULL AS IDENTITY to NUMBER(19) GENERATED BY DEFAULT ON NULL
AS IDENTITY.
Can you share more information about why a migration was generated? My
understanding is that the system check we just removed has complained
since 3.2 with instructions about the
[https://docs.djangoproject.com/en/5.2/releases/3.2/#customizing-type-of-
auto-created-primary-keys three ways] to avoid a migration (per model, per
app, or per project).
--
Ticket URL: <https://code.djangoproject.com/ticket/36687#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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019a17f42bb7-ff12b808-6f50-4a5b-a34a-095716248667-000000%40eu-central-1.amazonses.com.
