On 19 Lip, 10:35, Daniel Roseman <dan...@roseman.org.uk> wrote: > > I don't know why you think it's a bug. Django's models are - by design > - not an instantaneous reflection of the database. Rather, they only > interact with the DB when you load and save them. So this is the > expected behaviour.
So, should m.save() set m.id to some other value than None or this is relaxed when Warning exception is thrown? -- Tomasz Zieliński http://pyconsultant.eu --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
