#10227: Support a related_default on OneToOne fields
-------------------------------------+-------------------------------------
     Reporter:  rvdrijst             |                    Owner:  nobody
         Type:  New feature          |                   Status:  new
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |               Resolution:
     Severity:  Normal               |             Triage Stage:  Accepted
     Keywords:  onetoone related     |      Needs documentation:  0
  expection null                     |  Patch needs improvement:  0
    Has patch:  0                    |                    UI/UX:  0
  Needs tests:  0                    |
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by olau):

 Well, if the conceptual model is adding objects lazily, it's not really a
 problem that you need to save the user profile to get your changes to
 stick - they wouldn't stick otherwise. My example would never have worked
 without the save if the intention was to change the name persistently.

 But it's true that one would have to careful to make sure the user object
 was saved so it had an id. You have the same problem if you write the code
 manually, though.

 I had some trouble understanding your example on the difference to the
 foreign key default parameter - it seems what you are thinking about is a
 zero-or-one to one mapping, not a zero-or-one to zero-to-one (that would
 be related_default=None). Yes, it's less powerful in the related end in
 that you can't avoid confounding null and default. But there's no way
 around that. When I said relatively in line with the existing API, I just
 meant that the conceptual idea of returning an in-memory object when
 nothing exists yet was the same.

 Thanks for looking at this, by the way. :)

-- 
Ticket URL: <https://code.djangoproject.com/ticket/10227#comment:27>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to