oh yes, that makes sense! moved t.save() to just after its intialisation for better overview.
thanks a lot, Malcolm On Sun, Jul 6, 2008 at 2:01 PM, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > On Sun, 2008-07-06 at 13:36 +0200, Andre Meyer wrote: > [...] > > >>> t = SimpleTask() > > >>> t.title = 'first task' > > >>> t.done = False > > >>> n = SimpleNote() > > >>> n.title = 'first note' > > >>> n.text = "just some text for this note." > > >>> n.item = t > > At this point, t hasnt' been saved, so it won't have a pk value. > > > >>> n.save() > > Now you've just saved that NULL pk value. > > > >>> t.save() > > Only now is 't' really able to used in another object. Oops. Reverse the > order of saving the two things and things should work as expected. > > Regards, > Malcolm > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
