2010/6/9 Clovis Fabricio nos...@gmail.com:
2010/6/9 Michael Bayer mike...@zzzcomputing.com:
I think I know what the problem is. You need to use freetds version 7.0 or
8.0. If I set mine down to 4.2, I get your goofy results.
I'm away from the server right now, I'll do more tests tomorrow,
Michael, thanks for your answer.
2010/6/8 Michael Bayer mike...@zzzcomputing.com:
On Jun 8, 2010, at 5:38 PM, Clovis Fabricio wrote:
I'm aware that sqlalchemy 2005 has the DATE type, but sqlalchemy 2000
doesn't.
according to our source, DATE is only available on 2008, not 2005 or 2000.
I should gather all information before hitting send. Sorry for that;
print engine.execute(SELECT SERVERPROPERTY('productversion'),
SERVERPROPERTY ('productlevel'), SERVERPROPERTY
('edition')).fetchone()
returns:
('8.00.760', 'SP3', 'Enterprise Edition')
--
nosklo
--
You received this message
ah well that's the problem. this detection code might be wrong for 2005, 2008
as well.
If you want to try out this PyODBC code, perhaps we need to check with the
pyodbc list:
connection = pyodbc.connect(...)
print connection.getinfo(pyodbc.SQL_DBMS_VER)
On Jun 9, 2010, at 3:41 PM,
On Jun 9, 2010, at 5:42 PM, Michael Bayer wrote:
ah well that's the problem. this detection code might be wrong for 2005,
2008 as well.
If you want to try out this PyODBC code, perhaps we need to check with the
pyodbc list:
connection = pyodbc.connect(...)
print
2010/6/9 Michael Bayer mike...@zzzcomputing.com:
ah well that's the problem. this detection code might be wrong for 2005,
2008 as well.
If you want to try out this PyODBC code, perhaps we need to check with the
pyodbc list:
connection = pyodbc.connect(...)
print
2010/6/9 Michael Bayer mike...@zzzcomputing.com:
OK, here's something else to try, this would help with the pyodbc issue in
any case. Turn on ODBC logging (its a setting with your ODBC driver). You
should get a dumpfile like the one here:
On Jun 9, 2010, at 6:06 PM, Clovis Fabricio wrote:
2010/6/9 Michael Bayer mike...@zzzcomputing.com:
ah well that's the problem. this detection code might be wrong for 2005,
2008 as well.
If you want to try out this PyODBC code, perhaps we need to check with the
pyodbc list:
connection
2010/6/9 Michael Bayer mike...@zzzcomputing.com:
I think I know what the problem is. You need to use freetds version 7.0 or
8.0. If I set mine down to 4.2, I get your goofy results.
That could be the key problem, yes!
There's actions we can take here.
1. document that freetds version 7, 8
I'm connecting to mssql server 2000 through pyodbc, via FreeTDS odbc
driver, on linux ubuntu 10.04.
Sqlalchemy 0.5 uses DATETIME for sqlalchemy.Date() fields.
Now Sqlalchemy 0.6 uses DATE, but sql server 2000 doesn't have a DATE type.
I'm aware that sqlalchemy 2005 has the DATE type, but
On Jun 8, 2010, at 5:38 PM, Clovis Fabricio wrote:
I'm connecting to mssql server 2000 through pyodbc, via FreeTDS odbc
driver, on linux ubuntu 10.04.
Sqlalchemy 0.5 uses DATETIME for sqlalchemy.Date() fields.
Now Sqlalchemy 0.6 uses DATE, but sql server 2000 doesn't have a DATE type.
On Jun 8, 2010, at 5:38 PM, Clovis Fabricio wrote:
I'm connecting to mssql server 2000 through pyodbc, via FreeTDS odbc
driver, on linux ubuntu 10.04.
Sqlalchemy 0.5 uses DATETIME for sqlalchemy.Date() fields.
Now Sqlalchemy 0.6 uses DATE, but sql server 2000 doesn't have a DATE type.
12 matches
Mail list logo
