Re: Created & updated date/time in models

2012-08-12 Thread Lachlan Musicman
On Sun, Aug 12, 2012 at 12:06 PM, Melvyn Sopacua wrote: > On 8-8-2012 23:02, Lachlan Musicman wrote: > >> From what I can see, the admin interface already keeps this data for >> each object (exception: no create_date for data imported via fixtures >> apparently). > > Three options: > 1) Add the fi

Re: Created & updated date/time in models

2012-08-11 Thread Melvyn Sopacua
On 8-8-2012 23:02, Lachlan Musicman wrote: > From what I can see, the admin interface already keeps this data for > each object (exception: no create_date for data imported via fixtures > apparently). Three options: 1) Add the fields you want to each model 2) Bypass django and use triggers to pop

Re: Created & updated date/time in models

2012-08-09 Thread Lachlan Musicman
On Thu, Aug 9, 2012 at 3:33 PM, Dennis Lee Bieber wrote: > On Thu, 9 Aug 2012 09:02:39 +1200, Lachlan Musicman > declaimed the following in gmane.comp.python.django.user: >> >> From what I can see, the admin interface already keeps this data for >> each object (exception: no create_date for data

Re: Created & updated date/time in models

2012-08-08 Thread Mike Dewhirst
On 9/08/2012 7:02am, Lachlan Musicman wrote: Hola, I've got a bunch of date dependent data that I will need to analyse as the years go by. So adding create_date and update_date fields seems like the thing to do. I go researching I and I see that there are debates about whether auto_now_add and

Created & updated date/time in models

2012-08-08 Thread Lachlan Musicman
Hola, I've got a bunch of date dependent data that I will need to analyse as the years go by. So adding create_date and update_date fields seems like the thing to do. I go researching I and I see that there are debates about whether auto_now_add and auto_now are useful or whether they should be h