#9688: Date*Field IntegrityError 1048 column cannot be null
---------------------------------------------------+------------------------
Reporter: pierpaolodf | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: invalid | Keywords: DateField
DateTimeField null IntegrityError 1048
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by kmtracey):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm guessing you added one or both those options after the syncdb that
created the table. In which case you need to manually update the table
definition to say nulls are allowed, since changes like this that you made
to your model definitions post-syncdb aren't reflected in the DB
automatically. Reopen if you've got a recreatable scenario where a
blank=True,null=True !DateField is created by syncdb without allowing
nulls at the DB level, but I doubt that is what is happened.
--
Ticket URL: <http://code.djangoproject.com/ticket/9688#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
