[sqlalchemy] Re: 0.3.6 problem, was working with 0.3.4

Thanks Rick, I updated to the latest SVN rev and things do work now. Cheers, François On Apr 4, 10:08 pm, Rick Morrison [EMAIL PROTECTED] wrote: Hi fw, The explicit zero for the float column was a bug that should be fixed in rev #2491. MSSQL can store low-resolution datetimes in

[sqlalchemy] Re: 0.3.6 problem, was working with 0.3.4

Hi Rick, I am afraid I reported success a bit too fast. The problem has changed though. I am using rev 2492. If I use the MakerCost mapper as it is defined in my previous email, I get a strange behaviour: If I query a MakerCost directly (e.g. session.query(MakerCost).select_by(..))

[sqlalchemy] Re: 0.3.6 problem, was working with 0.3.4

Hi fw, The explicit zero for the float column was a bug that should be fixed in rev #2491. MSSQL can store low-resolution datetimes in DATE columns, and the format for MSSQL Date columns was expanded to allow storing those (note the missing seconds in the format). That date change should not