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
On Oct 5, 2011, at 10:13 PM, Simon Haines wrote:
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,
