this is a typing error; your PG database is giving richer information
for a particular type than the selected SQLAlchemy TypeEngine class
expects to receive. as far as what that type is and what the richer
information is, youd either have to put some debug print statements on
line 385 of postgres
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
> > co
>
> 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 fi
On Tuesday 19 December 2006 05:51, Alan Franzoni wrote:
> > >>> from sqlalchemy import *
> > >>> db = create_engine('postgres://user:[EMAIL PROTECTED]/test5')
> > >>> metadata = BoundMetaData(db)
> > >>> tb = Table('gffdata',metadata,autoload=True)
>
> This works fine on my system (ubuntu edgy, x8
>
> >>> from sqlalchemy import *
> >>> db = create_engine('postgres://user:[EMAIL PROTECTED]/test5')
> >>> metadata = BoundMetaData(db)
> >>> tb = Table('gffdata',metadata,autoload=True)
This works fine on my system (ubuntu edgy, x86, python 2.5, postgresql 8.1.4,
psycopg 2.0.5, SA 0.3.3), could
