On 19 Wrz, 16:37, Rob J Goedman <[EMAIL PROTECTED]> wrote: > Tomasz, > > The fixture is breaking with ' "2007-09-17 09:17:57.890755", ', after > revision 6329 it either > started to add the subseconds or can't read them anymore. Not sure if > there are more instances > of such a time format. Remove the .nnnnnn part to fix it. > > I've been running on r6329 for several days now and that seems to > work fine. Haven't tried > todays version yet. > > Regards, > Rob I've got the bug even with 6329. I don't know why, possibly because of using sqlite, and you wrote you're using postgresql. I guess there is datetime object converted to string using simple str() or unicode() call instead of using strftime, but see bunch of strftimes in django code, so I'm not sure. I know str() adds microseconds to string representation when nonzero...
Also some databases don't store microseconds, so str() will think microseconds==0 and will not add them, making json correct. That might be the difference between sqlite and postgres (i don't know the latter). Also I noticed that xml format is working well. That probably means xml doesn't use str() (if my hypothesis is correct). I haven't got much time for investigation though. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
