#28451: Change in Oracle sequence name truncation causes regression when 
existing database
     Reporter:  Kevin Grinberg       |                    Owner:  Kevin
                                     |  Grinberg
         Type:  Bug                  |                   Status:  assigned
    Component:  Database layer       |                  Version:  1.11
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:
     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 Kevin Grinberg):

 PRs - all tests pass under Oracle (the changes don't touch anything else).

 master: https://github.com/django/django/pull/8898
 backport to 1.11.x: https://github.com/django/django/pull/8899

 NB: The migration script in the backport may be a bit unwieldy to put in
 the release notes, particularly given that it likely affects very few
 people (basically ONLY users who created projects with 1.11, are on
 Oracle, and using use_returning_into=False). Is there a better standard
 place to put these sorts of things?

 I also omitted it from the master release notes, since it looks like we
 drop support for older versions of Oracle and stop relying on triggers

Ticket URL: <https://code.djangoproject.com/ticket/28451#comment:7>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to