Thanks Michael, you're correct I'm using pyodbc with FreeTDS, which doesn't
recognize the time datatype (and it seems FreeTDS doesn't support anything
above SQLServer 2005). And you're right, this is not a SQLAlchemy issue.
Sorry about that. I guess I can work around this by using
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
Thanks Michael,
On Friday, October 7, 2011 12:44:16 AM UTC+11, Michael Bayer wrote:
There are two things that come to mind that could specifically cause this
behavior.
One is, the identifier of 1 as an integer does not actually match the
datatype received back from the MSSQL database -
I'm fairly new to SQLAlchemy so I want to double-check this before filing
what I think is a bug against SQLAlchemy 0.7.
Consider a plain, declarative-mapped object:
class Table(Base):
__tablename__ = 'table'
id = Column(Integer, primary_key=True, nullable=False)
Now consider code to
