At 10:35 AM 10/13/2007, Greg wrote: [snip details of change to django code]
>That seems to fix the problem. Is the code that I took needed there >for a reason? Will this changed have an effect on how other areas of >my application work? Yes, that code is needed and is there for a reason. The object passed to that function should NOT be a unicode object, it ought to be a datetime object so that strftime can be called on it to properly format it. The bug is not the line of code you changed, it is whatever is causing a unicode object to be passed into the flatten_data function. I see from the archives you have brought this problem to the group before, but I don't see any resolution. I gather you are using sqlite, which, I'm sorry, I know nothing about so I can't really help you. For some reason you are getting back a unicode object from the db instead of a datetime. You say you just added this DateTime field to your model. Did you modify the table in sqlite yourself or did you re-initialize using django? It seems that either your version of sqlite is behaving oddly and returning a unicode string for something that ought to be a datetime object, or the field is not of the proper type in the database. Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
