On Jun 10, 2010, at 12:35 PM, Clovis Fabricio wrote:
> 2010/6/9 Clovis Fabricio :
>> 2010/6/9 Michael Bayer :
>>> 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'
2010/6/9 Clovis Fabricio :
> 2010/6/9 Michael Bayer :
>> 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, and
> send you the results.
ok, I
2010/6/9 Michael Bayer :
> 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 be used
> 2. have
On Jun 9, 2010, at 6:54 PM, Clovis Fabricio wrote:
> 2010/6/9 Michael Bayer :
>> 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:
>> http://www.eg
On Jun 9, 2010, at 6:06 PM, Clovis Fabricio wrote:
> 2010/6/9 Michael Bayer :
>> 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.conne
2010/6/9 Michael Bayer :
> 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:
> http://www.egenix.com/mailman-archives/egenix-users/2008-November/114471
2010/6/9 Michael Bayer :
> 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)
Res
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:
http://www.egenix.com/mailman-archives/egenix-users/2008-November/114471.html
If you see in that one, t
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 connectio
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, Clovi
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 mess
Michael, thanks for your answer.
2010/6/8 Michael Bayer :
> 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'm not 100% sure th
> 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
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 typ
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 sqlalch
15 matches
Mail list logo
