#22884: MySQL, unmanaged entity, does not get id after save()
-------------------------------------+-------------------------------------
     Reporter:  Jossef Harush        |                    Owner:  nobody
         Type:  Uncategorized        |                   Status:  closed
    Component:  Database layer       |                  Version:  1.6
  (models, ORM)                      |               Resolution:  duplicate
     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 claudep):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 This is expected behavior, core backends introspection is currently based
 on PEP 249's cursor.description, which doesn't allow us to introspect if
 the field is autoincrement or not. After fixing #21907, the output will
 now at least output a hint "# AutoField?" after the field to suggest the
 field type change during review.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22884#comment:2>
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/071.ae7bb182f0727af88ed507ef80cedd82%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to