On Jun 7, 4:30 pm, Luke Plant <l.plant...@cantab.net> wrote: > There seems to be the assumption in other messages in this thread that > Django 'owns' the database. That is not the philosophy Django takes - it
In the case of SQLite, it just plain sucks, because the DB is too stupid to support a true timestamp data type. On the other hand, this should have been foreseen when designing the Python SQLite API. I've not read anything about SQLite supporting true timestamps any time soon, so IMHO, something has to take ownership of this problem. Normally I would use Postgres for my Django apps, but I'm developing one in particular that will run on embedded Linux boxes, and they don't have the resource to run Postgres. > globally changing the format of how datetimes are stored in SQLite is > just not an option (at least not until Django 2.0), unless we can > guarantee backwards compatibility with existing data and other apps use > of the data. Backwards compatibility is always going to be a thorny issue for things that were not designed properly in the first place... As I suspected would be the case, I will probably roll my own custom field that handles this correctly, and maybe in a few years time somebody else will raise this issue... again. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
