I don't believe .create() allows you to say myforeignkey=1, correct me if I'm wrong, but I think it throws an error about it needing to be a <ForeigNkeyClass> instance.
On Sep 19, 11:30 am, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 9/19/07, David Cramer <[EMAIL PROTECTED]> wrote: > > > Yes, my biggest argument is I want to use .get_or_create() and I don't > > have an instance of the row (the id) I'm trying to insert. I'm *not* > > going to query for this instance (I'll write SQL before I add extra > > queries just to do an update/insert), and I don't like creating a fake > > temporary object, which will probably not work w/ the shared memory > > patch. (e.g. mykey=Model(id=3)) > > And it's been pointed out to you *twice* now that you don't have to > have an instance to do this. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
