On Thu, Mar 10, 2011 at 3:18 PM, octopusgrabbus <old_road_f...@verizon.net> wrote: > Could my problem be related to the fact that my views.py module first > performs a get (sql select) on the table in question, and if the > record is > not there, then inserts it?
No, it's probably because you are trying to set a datetime to a string, and the string is in a format that django cannot grok. You have failed to show any of the data or code, so all I can say about the date format you are using is that it is wrong. You should be using a datetime.datetime object anyway, rather than generating a string representation (badly). The entire purpose of using an ORM is to avoid these issues, but you seem intent on working around the ORM rather than through it. Cheers Tom -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
