Re: [Sqlalchemy-users] More DateTime woes

Ccing the person who contributed the psycopg1 patch for ticket #5Any reason why people might be stuck with psycopg1 ?  we are considering dropping support for it.On May 17, 2006, at 2:48 PM, Jonathan Ellis wrote:On 5/16/06, Rick Morrison <[EMAIL PROTECTED]> wrote: Speaking of psycopg1, is there

Re: [Sqlalchemy-users] More DateTime woes

On 5/16/06, Rick Morrison <[EMAIL PROTECTED]> wrote: Speaking of psycopg1, is there any good reason to continue support for that now that:   a) psycopg2 has been out of beta for some time? Federico has been pushing for people to upgrade.   b) SA requires Python 2.3, which has Std library datetime

Re: [Sqlalchemy-users] More DateTime woes

i didnt support psycopg1 at first but some folks needed it.  didnt dig too far into their reasoning since not much besides the mxDateTime adaption was needed.On May 16, 2006, at 5:16 PM, Rick Morrison wrote:Speaking of psycopg1, is there any good reason to continue support for that now that:   a)

Re[2]: [Sqlalchemy-users] More DateTime woes

Hey Rick, Unicode stuff doesn't work well in psycopg1 either. I'm all for not supporting it anymore, as making the mistake of starting off in it cost me a few days tracking down strange problems. It's documented in the wiki and in the mailing list, but I agree there's no good reason (besides ver

Re: [Sqlalchemy-users] More DateTime woes

I believe all of the database modules expect and return "native" Python datetime objects (which were added in Python 2.3). Import and use "datetime" instead of "mx.DateTime". See the Python docs for usage. Rick On 5/12/06, Dimi Shahbaz <[EMAIL PROTECTED]> wrote: Here is a test case that fails wi

Re: [Sqlalchemy-users] More DateTime woes

Speaking of psycopg1, is there any good reason to continue support for that now that:   a) psycopg2 has been out of beta for some time? Federico has been pushing for people to upgrade.   b) SA requires Python 2.3, which has Std library datetime support I was under the impression that psycopg2 is

Re: [Sqlalchemy-users] More DateTime woes

the DateTime types use Python datetime.datetime objects by default. they dont use mx.DateTime. only if youre using postgres with psycopg1 does an mx.DateTime module get used, otherwise its not. is mx.DateTime compatible with datetime.datetime ? the error you are getting would suggest the

[Sqlalchemy-users] More DateTime woes

Here is a test case that fails with the sqlalchemy-trunk. Create 2 files, in the first: import mx.DateTime as mxDateTime from sqlalchemy import * e = create_engine("postgres://database=test", echo=True) test = Table("test", e, Column("id", String, primary_key=True), Column("date", DateTi