#13966: sqlite orm problem with dates
---------------------------------------------------+------------------------
Reporter: leszek0140 | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: invalid | Keywords: date, orm,
sqlite
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => invalid
Comment:
The problem description is that when you put the wrong Django field over a
particular database field (DateTime's don't sit over the top of text
database columns), things behave unpredictably. This isn't a bug in
Django. AS noted, creating the correct database column type returns things
to normal behaviour. We shouldn't have to work around user errors of this
nature as it's on the same level as MySQL + MyISAM not enforcing
referential integrity. If you do something silly, you bear the
consequences.
--
Ticket URL: <http://code.djangoproject.com/ticket/13966#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.
