#31471: update_or_create object returns either an unparsed field (like a str) or
datetime for DateTimeField, depending on whether object is saved or not.
-------------------------------------+-------------------------------------
     Reporter:  Fonville             |                    Owner:  (none)
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  3.0
  (models, ORM)                      |               Resolution:
     Severity:  Normal               |  worksforme
     Keywords:  datetime, OneToOne   |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Fonville):

 Thanks for your explanation with the past ticket.
 Maybe it is good to document somewhere these kind of gotchas that
 (underwater) `.save()` can change the fieldtypes of the model object.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31471#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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.515b4bcff9065a73935ae4b6f622e695%40djangoproject.com.

Reply via email to