From 5f6ed1a3f8bb0b2a724c7f07b98936433a3ef053 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Sun, 15 Nov 2009 19:20:22 +0000 Subject: - pg8000 + postgresql dialects now check for float/numeric return types to more intelligently determine float() vs. Decimal(), [ticket:1567] - since result processing is a hot issue of late, the DBAPI type returned from cursor.description is certainly useful in cases like these to determine an efficient result processor. There's likely other result processors that can make use of it. But, backwards incompat change to result_processor(). Happy major version number.. --- lib/sqlalchemy/dialects/mssql/adodbapi.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lib/sqlalchemy/dialects/mssql/adodbapi.py') diff --git a/lib/sqlalchemy/dialects/mssql/adodbapi.py b/lib/sqlalchemy/dialects/mssql/adodbapi.py index 10b8b33b3..6ca1879d6 100644 --- a/lib/sqlalchemy/dialects/mssql/adodbapi.py +++ b/lib/sqlalchemy/dialects/mssql/adodbapi.py @@ -3,7 +3,7 @@ from sqlalchemy.dialects.mssql.base import MSDateTime, MSDialect import sys class MSDateTime_adodbapi(MSDateTime): - def result_processor(self, dialect): + def result_processor(self, dialect, coltype): def process(value): # adodbapi will return datetimes with empty time values as datetime.date() objects. # Promote them back to full datetime.datetime() -- cgit v1.2.1