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 tom
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
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
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
I'd like to add more information to the question:
>>> print sqlalchemy.Date().get_dbapi_type(sqlalchemy.dialects.mssql)
That seems to imply that it should use DATETIME, but it is not...
nosklo
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To
There's a typo in my message:
> I'm aware that sqlalchemy 2005 has the DATE type, but sqlalchemy 2000 doesn't.
It should read:
> I'm aware that MSSQL 2005 has the DATE type, but MSSQL 2000 doesn't.
Sorry for that.
nosklo
--
You received this message because you are subscribed to the Google Gr
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
2009/5/19 Daniel :
> Hello,
> I have a stored procedure for SQL Server and I would like to be able
> to execute the code to create the stored procedure using SA. Here's
> the basic idea.
> The problem is that I'm getting an error complaining about invalid
> syntax "ProgrammingError: (ProgrammingE
2009/2/11 Michael Bayer :
>
>
> On Feb 11, 2009, at 8:43 AM, Clovis Fabricio wrote:
>
>>
>> 2009/2/11 Clovis Fabricio :
>>> 2009/2/10 Michael Bayer :
>>>>> Question is: How can I do that in a sa.Table constructor?
>>>>> sa.Table
2009/2/11 Clovis Fabricio :
> 2009/2/10 Michael Bayer :
>>> Question is: How can I do that in a sa.Table constructor?
>>> sa.Table('DataB.dbo.TableInB', metadata, )
>>> sa.Table('TableInB', metadata, , schema='DataB.dbo')
2009/2/10 Michael Bayer :
>> Question is: How can I do that in a sa.Table constructor?
>> sa.Table('DataB.dbo.TableInB', metadata, )
>> sa.Table('TableInB', metadata, , schema='DataB.dbo')
>> And both failed. Is there a way to map tables from both databases
>> using the same engine? So I c
13 matches
Mail list logo
