On 13 oct, 17:15, Brian Beck <[EMAIL PROTECTED]> wrote:
> On Oct 13, 8:38 am, "Mike Scott" <[EMAIL PROTECTED]> wrote:
>
> > Secondly this question has been asked, and solved many times. If you search
> > through the django-users archives I'm sure you'll find plenty of solutions.
> > There are solu
On Mon, 2008-10-13 at 08:18 -0700, Brian Beck wrote:
> On Oct 13, 11:15 am, Brian Beck <[EMAIL PROTECTED]> wrote:
> > The only action was three months ago with a DeprecationWarning patch that
> > isn't checked in.
>
> ...and probably shouldn't be, since it still doesn't update the docs.
The fa
On Oct 13, 11:15 am, Brian Beck <[EMAIL PROTECTED]> wrote:
> The only action was three months ago with a DeprecationWarning patch that
> isn't checked in.
...and probably shouldn't be, since it still doesn't update the docs.
--~--~-~--~~~---~--~~
You received this
On Oct 13, 8:38 am, "Mike Scott" <[EMAIL PROTECTED]> wrote:
> Secondly this question has been asked, and solved many times. If you search
> through the django-users archives I'm sure you'll find plenty of solutions.
> There are solutions out and about in the blogosphere too.
Actually I think this
Thierry,
Firstly django-developers is not the place for this discussion.
Secondly this question has been asked, and solved many times. If you search
through the django-users archives I'm sure you'll find plenty of solutions.
There are solutions out and about in the blogosphere too.
Cheers,
Mik
Hi,
I have a lot of models using this type of fields :
creation = models.DateTimeField(auto_now_add=True)
update = models.DateTimeField(auto_now=True)
But I read that since 2007, it was planned to drop those options from
models.DateField.
Here the post :
http://groups.google.com/grou
