On Tuesday 19 December 2006 08:05, Alan Franzoni wrote:
I played a bit more and it happens only with a particular database. When
connecting to another database, it seems to work just fine. I'll look
into
it more here, as it seems to be idiosyncratic. If I come to any hard
conclusions, I'll forward them along.
By taking a look at the file, I guess this could be a column/arguments
mismatch. In a debug session, put a breakpoint at line 385 in
postgres.pyand take a look at what 'attype' is and at the value of
'args' and 'kwargs'.
Also, please remember that this glitch could be postgresql-related. 8.2 is
very new, and I don't know if either SQLAlchemy or psycopg2 are well-tested
against it. You could try another DB-adapter as well.
Thanks again, Alan. You are probably correct here. If I do track down the
cause, I'll forward it along.
Sean
6 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: Misunderstanding som...