trunk, sqlite backend bug with date handlig

2007-07-07 Thread Andrey Khavryuchenko
Hi! Had anyone noticed that loading DateField and DateTimeField from sqlite in-memory db results in getting plain strings instead of datetime objects? Code: f = models.Feed(feed_url='no such url', is_active=True) f.save() post = models.Post(feed = f, title='test post', l

Re: trunk, sqlite backend bug with date handlig

2007-07-07 Thread Malcolm Tredinnick
On Sat, 2007-07-07 at 20:57 +0300, Andrey Khavryuchenko wrote: > Hi! > > Had anyone noticed that loading DateField and DateTimeField from sqlite > in-memory db results in getting plain strings instead of datetime objects? > > Code: > > f = models.Feed(feed_url='no such url', is_active=T

Re: trunk, sqlite backend bug with date handlig

2007-07-07 Thread Andrey Khavryuchenko
MT> On Sat, 2007-07-07 at 20:57 +0300, Andrey Khavryuchenko wrote: >> While I'm digging in sqlite backend sources, may anyone share his >> experience? MT> I just tried this with some models I have here using sqlite and they all MT> loaded DateTime fields as Python datetime instances. Saving

Re: trunk, sqlite backend bug with date handlig

2007-07-07 Thread Malcolm Tredinnick
On Sat, 2007-07-07 at 23:04 +0300, Andrey Khavryuchenko wrote: > > MT> On Sat, 2007-07-07 at 20:57 +0300, Andrey Khavryuchenko wrote: > >> While I'm digging in sqlite backend sources, may anyone share his > >> experience? > > MT> I just tried this with some models I have here using sqlite an

Re: trunk, sqlite backend bug with date handlig

2007-07-07 Thread Andrey Khavryuchenko
Malcolm, Thanks, your answers helped to trace down the problem. It appeared that just sqlite connection was opened without proper 'detect_types' parameter. MT> On Sat, 2007-07-07 at 23:04 +0300, Andrey Khavryuchenko wrote: >> MT> On Sat, 2007-07-07 at 20:57 +0300, Andrey Khavryuchenko wrot