#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: new
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Normal | Resolution:
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 Mariusz Felisiak):
* severity: Release blocker => Normal
--
Ticket URL: <https://code.djangoproject.com/ticket/36687#comment:2>
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/0107019a173ad97c-fe846b73-dedf-4546-ba2e-be0ca14d15df-000000%40eu-central-1.amazonses.com.
