James Bennett wrote:
> Default values are *only* filled in when the field is displayed on an
> end-user form. If you don't want to display a field, but still
> automatically fill it in, you have two options:
>
> 1) Have your view code fill it in before doing manipulator validation
> 2) Set 'blank
On 9/26/06, Mongo <[EMAIL PROTECTED]> wrote:
> I would like it to appear as if it was a default value for the object,
> to be honest. :) And by that I mean I would like to be able to display
> the default-value of date_created on the create page (and the actual
> date_created of the object on an e
I would like it to appear as if it was a default value for the object,
to be honest. :) And by that I mean I would like to be able to display
the default-value of date_created on the create page (and the actual
date_created of the object on an edit page.)
Doing it in save() doesn't help. Doing it
On 9/26/06, Mongo <[EMAIL PROTECTED]> wrote:
> Which works when presenting the "create" page to the user, but when
> they submit, the "new_data = request.POST.copy()" causes new_data to be
> constructed without date_created, causing an error when I try to save
> since it.
Default values are *only
What's the proper way to create a field which is set to the date the
object was created via a web view?
I tried doing this in the model:
def Today():
return datetime.date.today()
date_created = models.DateField(default=Today)
Which works when presenting the "create" page to the user, but
5 matches
Mail list logo
