> -----------------------------------------------------------
> from MySQLdb import Warning as Warning
> from django.db import models
> import unittest

> class TestModel(models.Model):
>     char_field = models.CharField(max_length=5)

> class Case1(unittest.TestCase):
>     def test1(self):
>         print "Count 1:", TestModel.objects.count()
>         m = TestModel(char_field="123456")
>         try:
>             m.save()
>         except Warning:
>             print "Count 2:", TestModel.objects.count()
>             print "m.id=", m.id
>             print "all()[0].id=", TestModel.objects.all()[0].id
> -----------------------------------------------------------

> manage.py test returns:

> Count 1: 0
> Count 2: 1
> m.id= None
> all()[0].id= 1

> Which seems like a bug to me (m.id=None). Am I right or I overlooked
> some info in documentation?

> --
> Tomasz Zielińskihttp://pyconsultant.eu

> 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?

> 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.

> 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

> > 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.