Is there a different way to do this that's compatible with both
versions, or is there a new 0.4 way of doing this, or have I just been
doing something wrong all along and only 0.4 is catching it?
DateTime objects in sqlite currently expect a datetime.datetime
object, and not a string.
On Aug 16, 10:06 am, JP [EMAIL PROTECTED] wrote:
What's odd here is that I'm not setting the value myself -- it's
getting set in pre_exec by the column default, which (I believe) is
running the func in sqlite and returning the results, which I'd think
should wind up with a
ok thats in r3322
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
Yup, that fixed things. Thanks!
On Aug 16, 10:49 am, Michael Bayer [EMAIL PROTECTED] wrote:
ok thats in r3322
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
On Aug 15, 2007, at 6:22 PM, JP wrote:
Is there a different way to do this that's compatible with both
versions, or is there a new 0.4 way of doing this, or have I just been
doing something wrong all along and only 0.4 is catching it?
DateTime objects in sqlite currently expect a
