On 25 Nov., 00:36, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > Why would it be? A datetime field isn't necessarily stored in UTC. It > uses datetime.now() because that will return the same time as > settings.TIME_ZONE.
To improve my understanding: What if the server changed and the time zone is not the same? IMHO the user can choose: 1. leave the settings.TIME_ZONE to the old value, so all old datetimes are right, but new datetimes are wrong. Or 2. he can update settings.TIME_ZONE and old datetimes would be wrong, but new are right. Isn't it? > On top of that, making this change would be a *huge* backwards > incompatibility, as any existing uses of auto_now etc would break. Yes. But it's easy to add a settings and the admin can choose between now or utcnow. The default settings should be set utcnow. Mfg. Jens Diemer -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
