#22665: Creating trigger in custom sql for mySQL failed with 1046 error
-------------------------------------+-------------------------------------
     Reporter:  hudan@…              |                    Owner:  nobody
         Type:  Uncategorized        |                   Status:  closed
    Component:  Database layer       |                  Version:  1.6
  (models, ORM)                      |               Resolution:  invalid
     Severity:  Normal               |             Triage Stage:
     Keywords:                       |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by timo):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 It's not clear to me that this is a bug in Django. Also, initial SQL is
 deprecated now that we have migrations in 1.7+ so even if there is a bug,
 we probably wouldn't fix it at this point.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22665#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/079.75daffc26d47e9cf5626925d918bca0b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to