#3997: Missing default value causes exception on save
------------------------------------------------------+---------------------
Reporter: Henrik Vendelbo <[EMAIL PROTECTED]> | Owner: adrian
Status: new | Component: Database
wrapper
Version: SVN | Keywords:
Stage: Unreviewed | Has_patch: 0
------------------------------------------------------+---------------------
Using MySQL I have noticed a common cause for save to fail. Especially
BooleanField's with no default value. If there is no default value, MySQL
will return a Warning for data truncation, which will cause the save to
fail. I believe that I tried to catch MySQLdb.Warning and pass on it with
no improvement.
1) A warning should not cause the transaction to fail
2) If a default value is effectively required, validate should check for
it
--
Ticket URL: <http://code.djangoproject.com/ticket/3997>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
