Brett Hoerner wrote: > Robert Wittams wrote: > >>both auto_now and auto_now_add are quite hackish little puppies. >> >>auto_now should really be equivalent to a _pre_save that sets the field >>to the current time. >> >>auto_now_add should really be equivalent to a non-editable field that >>gets set to the current time on insert, and is just statically displayed >>afterwards. > > > I think you got them reversed, I think auto_now currently works as > intended. If you display it (your mistake I guess?) and edit it, it > will still cram in the current time on insert. >
Erm, no. I was talking about the internal implementation of these options. Even though they do work in some situations, they are hacky and do need to be cleaned up at some point. By "insert" I mean the initial creation of a tuple with that id in the database, not subsequent updates of it.
