Hi,
unfortunately my time-limited trial license of the easysoft driver
already expired so i cannot check it further.
thanks anyway for your wilingness to help.
regards,
stefan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goo
Hi,
If it helps any, maybe turn on some driver tracing. In the odbc.ini
entry set
Logging = Yes
LogFile = /tmp/sql.log
And maybe send it to Easysoft (if you haven't already)
As one of the Easysoft developers of that driver, and the PM of
unixODBC, I am sure we can sort something out. Or at lea
shame on me I omit your "...addng the keyword parameter...", i.e.
db_mssql = create_engine( 'mssql://sa:[EMAIL PROTECTED]
use_scope_identity=1', module= pyodbc)
unfortunately with scope identity it crashes earlier - mssql.py
returns None for id and rollbacks.
best regards
stefan
--~--~--
hmm it gives with use_scope_identity=False and r2746:
File "/home/stefanb/src/hor/sqlalchemy/engine/strategies.py", line
106, in create
raise TypeError("Invalid argument(s) %s sent to create_engine(),
using configuration %s/%s/%s. Please check that the keyword arguments
are appropriate for
Che,
>trying SA with MSSQL Express through unixODBC/pyODBC encountered the
>following problem:
>
>
Well, your test script works fine for me on Windows, but you probably
knew that already.
You should expect to hit a lot of problems using MSSQL from Unix. For
now, I suggest you have a go with
Sounds like the "invalid cursor state" bug that I thought might have been
fixed for pyodbc in r2729. Maybe not...
Try adding the keyword parameter
use_scope_identity = False
to the create_engine() call and see if that clears it up.
On 6/15/07, che <[EMAIL PROTECTED]> wrote:
>
>
> forgot
forgot to mention that SA is at revision r2733.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, se
