[sqlalchemy] Users of sqlalchemy-migrate

2011-10-30 Thread Jan Dittberner
Hello, I'd like to add a list of projects that use sqlalchemy-migrate[1] to our project website in a way similar to the SQLAlchemy website [2]. I know of TurboGears 2 [3] and OpenStack [4] but would be interested in other projects too. If you have a publicly available website I would link to

[sqlalchemy] Problem/bug with column_property on eagerloaded polymophic table

2011-10-30 Thread Adrian Tejn Kern
I have a column_property on a polymorphic base class. When I joinedload/subqueryload a derived class the colum_property makes the query fail. class A(Base): __tablename__ = a id = Column(Integer, primary_key=True) type= Column(String(40), nullable=False) __mapper_args__

Re: [sqlalchemy] Problem/bug with column_property on eagerloaded polymophic table

2011-10-30 Thread Michael Bayer
It's a bug but a small one... I'd be ready to jump off a bridge if this kind of thing wasn't working in general at this point. Trying your test case, the column_property() for the moment has to be against the actual Column, not the mapped property (there's a difference): class A(Base):

[sqlalchemy] Querying mssql time columns

2011-10-30 Thread Simon Haines
I think I've found a bug--can anyone else confirm this? It appears that SQLAlchemy cannot query SQLServer time columns because Python datetime.time objects are always promoted to full datetime types. Once promoted the SQLServer returns the error: 'The data types time and datetime are

Re: [sqlalchemy] Querying mssql time columns

2011-10-30 Thread Michael Bayer
On Oct 31, 2011, at 1:18 AM, Simon Haines wrote: I think I've found a bug--can anyone else confirm this? It appears that SQLAlchemy cannot query SQLServer time columns because Python datetime.time objects are always promoted to full datetime types. Once promoted the SQLServer returns the