Re: [SQLObject] datetime column conversions

[Oleg B. <ph...@ma...>]

On Wed, Jan 05, 2005 at 01:01:01PM -0500, Barry Warsaw wrote:
> I'm having one immediate problem though.  I have a DateTimeCol in one of
> my tables, and I set that column to an instance of a datetime.datetime
> object.  That's all fine and good because SQLObject turns that into a
> string and stores it properly in the SQLite database.  However, when I
> retrieve the column's value, I get a string back, not a datetime.

   You are just in time! Please look the archive for this mailing list
and reread messages for the last few days - the discussion about
string-to-int conversion in the IntCol. Just today I commited a number
of patches.

   Your problem is unfortunately a bit harder - what should toPython()
returns - a string? a datetime instance? a mx.DateTime instance?
Currently the column returns whatever the underlying driver returns.
What database and driver do you use?

   Check out the code from Subversion's trunk and give it a try - there
were a lot of bugs fixed since the release of SQLObject 0.6.

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.