#5535: .get() should allow myforeignkey_id lookups
------------------------+---------------------------------------------------
Reporter: dcramer | Owner: nobody
Status: reopened | Component: Database wrapper
Version: SVN | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------+---------------------------------------------------
Comment (by dcramer):
The benefit is you don't need an instance of the object to call it.
If you use .create() you need an instance, unless you pass it as !_id, if
you use .get you don't need an instance.
If you use .get_or_create, you are forced to have an instance as .create
requires it, and .get doesn't handle !_id.
A dirty hack is saying
MyModel.objects.get_or_create(foreignkey=SomeModel(id=5)) but it's quite
unneeded and could cause problems w/ the shared memory patch.
--
Ticket URL: <http://code.djangoproject.com/ticket/5535#comment:11>
Django Code <http://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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
