#28451: Change in Oracle sequence name truncation causes regression when
updating
existing database
-------------------------------------+-------------------------------------
Reporter: Kevin Grinberg | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: oracle | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
Oracle backend uses `last_insert_id` only when `use_returning_into` is
disabled manually in database settings (see
[https://docs.djangoproject.com/en/1.11/ref/databases/#insert-returning-
into doc]), otherwise `_get_sequence_name` shouldn't affect insert
operation. Nevertheless, I think we should revert `_get_sequence_name` and
`_get_trigger_name` to the previous behavior (with suffixes) and add a
detailed instruction how to change (recreate) objects with wrong names.
--
Ticket URL: <https://code.djangoproject.com/ticket/28451#comment:1>
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/067.c47768f097f1c7ff53ef97b5efb628d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
