#28451: Change in Oracle sequence name truncation causes regression when 
updating
existing database
-------------------------------------+-------------------------------------
     Reporter:  Kevin Grinberg       |                    Owner:  Kevin
                                     |  Grinberg
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  1.11
  (models, ORM)                      |
     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 Tim Graham <timograham@…>):

 In [changeset:"90be8cf2a4d81005c5c35074ba763f5fd3a56bd1" 90be8cf2]:
 {{{
 #!CommitTicketReference repository=""
 revision="90be8cf2a4d81005c5c35074ba763f5fd3a56bd1"
 [1.11.x] Fixed #28451 -- Restored pre-Django 1.11 Oracle sequence/trigger
 naming.

 Regression in 69b7d4b116e3b70b250c77829e11038d5d55c2a8.

 Backport of c6a3546093bebae8225a2c5b7e0836a2b0617ee5 from master
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/28451#comment:10>
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 
https://groups.google.com/d/msgid/django-updates/067.e3dc9a03aacc6febbb7791b62d73a22f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to