#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 ubernostrum):

 If you're back to `create` and `get_or_create`, then again this is a
 "worksforme": you can use the `_id` syntax just fine there, and I don't
 know why you keep trying to bring that up. In `create` you can pass it
 directly, and in `get_or_create` you can pass it in `defaults`. And
 there's nowhere else you need an instance, because the `__id` syntax for
 lookups works just fine with the actual primary-key value.

 So, again: where's the gain? What can't you do right now that you could do
 if we changed the lookup syntax?

-- 
Ticket URL: <http://code.djangoproject.com/ticket/5535#comment:12>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to