Thank you very much for all the responses. I found the source of the problem in my code.
I was adding a property to Model Model.revision = property(fget=XXX, fset=YYY) which conflicted with the revision field I was having trouble with. Sorry for the confusion. Best, AG On Aug 10, 2:22 pm, Karen Tracey <kmtra...@gmail.com> wrote: > On Mon, Aug 10, 2009 at 2:13 PM, ankit rai <ankit9...@gmail.com> wrote: > > check ur db table ,is null=true present.And in ur model write > > revision = models.IntegerField(default=0,balnk=true,null=true) > > and if u donont want to change the value from 0 at all then there is no > > need to diplay it in fields > > null=True should not be present. AG doesn't want null values allows but > rather wants them to be set to a default value. > > Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
