#15842: Silent Failure of InlineAdmin Class With a DateTimeField on the Model if
Only a "time with timezone" Column in the Database
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
vincitveritas | Status: closed
Type: Bug | Component: Database layer
Milestone: | (models, ORM)
Version: 1.2 | Severity: Normal
Resolution: wontfix | Keywords:
Triage Stage: | Has patch: 0
Unreviewed | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => wontfix
* easy: => 0
Comment:
Generally Django does not attempt anything to warn you of inconsistencies
between your models and your database.
Even something as gross as replacing a !TextField by an !IntegerField will
only result in exceptions at runtime, possibly in unexpected places.
It is hard to debug, but I think it is a consequence of (1) Python's type
handling and (2) Django's choice not to use database introspection.
Solving this problem would require some database introspection. I think
the core devs will reject the idea, but you can always bring it on django-
developers to be sure.
--
Ticket URL: <http://code.djangoproject.com/ticket/15842#comment:2>
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.
