> On 14 mrt, 01:40, "Honza Kr=E1l" <[EMAIL PROTECTED]> wrote:
>
> for this use DateField( default=3Dmodels.LazyDate() ), it will do
> exactly what you want: supply a default value of NOW() when no
> timestamp is given.
>
> It seems redundant to replicate this with the auto_* stuff, those are
> me
> On 14 mrt, 01:40, "Honza Kr=E1l" <[EMAIL PROTECTED]> wrote:
>
> for this use DateField( default=3Dmodels.LazyDate() ), it will do
> exactly what you want: supply a default value of NOW() when no
> timestamp is given.
>
> It seems redundant to replicate this with the auto_* stuff, those are
> mea
> On 14 mrt, 01:40, "Honza Král" <[EMAIL PROTECTED]> wrote:
>
> for this use DateField( default=models.LazyDate() ), it will do
> exactly what you want: supply a default value of NOW() when no
> timestamp is given.
>
> It seems redundant to replicate this with the auto_* stuff, those are
> meant
On 3/13/07, Norjee <[EMAIL PROTECTED]> wrote:
>
> Both have the behaviour that "the current date is always used". For
> auto_now, it meas it is impossible to set a custom timestamp. For
> auto_now_add it means you first have to create the object, save it,
> set custom stamp, save again.
>
> First i
Both have the behaviour that "the current date is always used". For
auto_now, it meas it is impossible to set a custom timestamp. For
auto_now_add it means you first have to create the object, save it,
set custom stamp, save again.
First it is odd that if it is intended for the timestamp to be wr
