auto_now_add field NULL on update

Hi, I have a model with a field defined as created = models.DateTimeField(auto_now_add = True) Problem is that when an object of this type is updated, the UPDATE query has a clause like "created"=NULL which is violating the NOT NULL constraint on the field. I was under the impression

Field Description in FormWrappers

Hi, Is it possible to retrieve the description of a field in a FormWrapper in the template? I'm able to get the field name using {{ form.field.field_name }}, but I'd like the verbose name to appear on the form. Regards -fawad --~--~-~--~~~---~--~~ You rece

Re: Model module naming in m-r

On Mon, April 10, 2006 16:53, Luke Plant wrote: > > On Monday 10 April 2006 14:37, Fawad Halim wrote: > > >> I was trying to port an existing (0.91) app to the m-r branch, and >> found that apparently, the m-r branch requires the models to reside in >> models.py di

Re: Model module naming in m-r

On Mon, April 10, 2006 09:01, James Bennett wrote: > > On 4/10/06, Fawad Halim <[EMAIL PROTECTED]> wrote: > >> I was trying to port an existing (0.91) app to the m-r branch, and >> found that apparently, the m-r branch requires the models to reside in >>

Model module naming in m-r

Hi all, I was trying to port an existing (0.91) app to the m-r branch, and found that apparently, the m-r branch requires the models to reside in models.py directly under the app directory (django.db.models.base.ModelBase explicitly checks for the model module name ending in .models). Is this a