On Wed, Aug 23, 2017 at 5:00 PM, Richard Postelnik wrote:
> I was looking into an issue with a package and noticed that what was
> supposed to be an MSSQL timestamp specific case was being applied to all
> timestamps. Upon further investigation I found that the mssql.TIMESTAMP was
> equal to sa.TI
I was looking into an issue with a package and noticed that what was
supposed to be an MSSQL timestamp specific case was being applied to all
timestamps. Upon further investigation I found that the *mssql.TIMESTAMP* was
equal to *sa.TIMESTAMP*. Both yield a *sqlalchemy.sql.sqltypese.TIMESTAMP*.