On 4/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I even tried just returning datetime.datetime.now() from within the
> view, and that worked. But when I try to save it to the database, it's
> null.
This is a tricky one to spot, but I think it has to do with the format
the manipulator system expects. Before the call to 'do_html2python'
happens, the manipulator expects the data to be in the format an HTTP
POST would have produced, which in the case of a DateTimeField means
two values, both strings, representing the date and the time. So a
Python 'datetime' object will not work at that point --
'do_html2python' wants a date string and a time string, and it will
convert them into a single 'datetime' object.
The correct format is for new_data to have keys
'topic_modification_date_date' and 'topic_modification_date_time'; the
date part should be in 'yyyy-mm-dd' format (e.g., '2007-04-17' for
April 17 2007), and the time part should be in 'hh:mm:ss' format
('09:10:23', for example). Then 'do_html2python' will turn them into a
valid datetime value for the field.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
