#24892: Django migrations don't escape uppercase table name in "" when using
postgres backend when changing Integer  field to Auto field
---------------------------------+-------------------------------------
     Reporter:  jbzdak           |                    Owner:  timgraham
         Type:  Bug              |                   Status:  closed
    Component:  Migrations       |                  Version:  1.8
     Severity:  Release blocker  |               Resolution:  fixed
     Keywords:                   |             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:"8911d2e20fc5f4fc7b0274594813ed0b1ad8bc6b" 8911d2e2]:
 {{{
 #!CommitTicketReference repository=""
 revision="8911d2e20fc5f4fc7b0274594813ed0b1ad8bc6b"
 [1.8.x] Fixed #24892 -- Fixed quoting of SQL when renaming a field to
 AutoField in PostgreSQL

 Backport of 5ab86809832726957dd6f0eb8e17a461f0a9be84 from master
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/24892#comment:5>
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/064.6d059ace10827c3e042149610e464a27%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to