On 5/29/06, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote: > Hi Konstantin, > > On 5/29/06, Konstantin Shaposhnikov <[EMAIL PROTECTED]> wrote: > > I suggest you to not use auto_now_add at all if you are using current > > (post magic-removal) version of django. > > I am using the SVN trunk yes. (It would be great if someone could > finally fix trunk's setup.py to reflect what manage.py states about > versioning.) > > [snip excellent suggestion] > > > I am not really sure, but I seen somewhere that auto_now and > > auto_now_add are going to become deprecated and it makes sense taking > > into account that it is possible to achieve given functionlaity in > > other way and code that supports auto_now[_add] is full of hacks. > > I couldn't find such statement quickly, so if anyone can please update > the list on this issue, thanks.
I've seen it here http://code.djangoproject.com/ticket/1056 (see the first comment by jacob) Though I am not sure how actual this statement is. Ticket seems to be quite old. > Thanks Konstantin, I will play around with that. > > -- > Jeroen Ruigrok van der Werven > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
