On Thu, 2007-10-25 at 11:07 -0700, ZebZiggle wrote:
> Thanks Karen ... do you of a way to override this behavior?
>
> I can think of many situations where you would want to be able to
> modify it.
auto_now and auto_now_add *always* set the automatic value, they don't
supply default values you
Thanks Karen ... do you of a way to override this behavior?
I can think of many situations where you would want to be able to
modify it.
-Z
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
Specifying auto_add_now=True makes the field non-editable. Therefore the
admin won't include it in the fields on a change page or in an edit-inline
section.
Karen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
I'm having the same/similar problem. I have a field
created = models.DateTimeField(auto_now_add = True)
which doesn't show up in the admin interface, but everything else
does ... including other datetime fields (just not auto_add_now).
The field exists in the database, is used and getting
Hello,
I have a table called Orders. Which stores information about each
order that I get. It also has the ability to send email's to the
customer's email address. I also have another table called EmailSent
that store information about each email that I send through the
admin. My EmailSent
5 matches
Mail list logo
