On 19 Lip, 18:32, Alex Gaynor <alex.gay...@gmail.com> wrote: > 2009/7/19 Tomasz Zieliński <tomasz.zielin...@pyconsultant.eu>: > > > > > > > On 19 Lip, 16:29, Joshua Russo <josh.r.ru...@gmail.com> wrote: > >> 2009/7/19 Tomasz Zieliński <tomasz.zielin...@pyconsultant.eu> > > >> > So, should m.save() set m.id to some other value than None > >> > or this is relaxed when Warning exception is thrown? > > >> It's the database that gives m.id a value upon a valid save. So because the > >> record couldn't be saved it never received a value. > > > The record is saved - what is raised is Warning (about string being > > truncated), not Error. > > > As a proof, following instruction prints 1: > > > print "all()[0].id=", TestModel.objects.all()[0].id > > > -- > > Tomasz Zieliński > >http://pyconsultant.eu > > I believe this is just a shortcoming of either MySQL, or MySQLDb, in > that it can't return the ID of an inserted object. >
Thanks, I'll check it down the pipeline then. -- 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 -~----------~----~----~----~------~----~------~--~---
