this is something occurring within the DBAPI you're using, i.e. pyodbc, pymssql, etc. you'd need to compose a simple test case using only the DBAPI (else the DBAPI authors will suspect its on SQLAlchemy's side) and report it to them.
if a plain DBAPI test does not reproduce the problem, send it over here and we can compare the plain DBAPI case to the SQLAlchemy case. unlikely here since SQLA doesn't do anything with ints coming back from the database. On Oct 13, 2011, at 3:27 AM, Matt Bodman wrote: > I have a SMALLINT column in MSSQL. The value of the column is -2 > > SQLAlchemy also has the column as SMALLINT but the value is translated as > 4294967294 > > I can't seem to correct this and I haven't found anything on SA and negative > numbers. Any help would be really great, thanks. > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/sqlalchemy/-/F49ec3O3IGkJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
