Re: [Sqlalchemy-tickets] [sqlalchemy] #2909: support MS ODBC for linux / Connection is busy with re
Brought to you by:
zzzeek
|
From: sqlalchemy <mi...@zz...> - 2014-01-13 15:44:17
|
#2909: support MS ODBC for linux / Connection is busy with results for another
command
-------------------------------------------+-------------------------------
Reporter: tuomur | Owner: zzzeek
Type: defect | Status: new
Priority: high | Milestone: 0.9.xx
Component: mssql | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: needs questions answered |
-------------------------------------------+-------------------------------
Changes (by zzzeek):
* severity: no triage selected yet => major - 1-3 hours
* component: engine => mssql
* priority: medium => high
* milestone: => 0.9.xx
* status_field: awaiting triage => needs questions answered
Comment:
correct me if I'm wrong, this doesn't seem at all like any issue with
reflecting tables; the reflection works fine. Something is specifically
wrong with either your second data source or just having an application
that's talking to two datasources at once.
let's keep it simple. run this:
{{{
import sqlalchemy as sa
e1 = sa.create_engine('mssql+pyodbc://user:pass@work_database',
logging_name='work',
echo=True)
e2 = sa.create_engine('mssql+pyodbc://user:pass@terrain_database',
logging_name='terrain',
echo=True)
e1.execute("select 1").fetchall()
e2.execute("select 1").fetchall()
}}}
a. does it crash and b. does it crash only on the second engine? in that
case, how about:
{{{
import sqlalchemy as sa
e2 = sa.create_engine('mssql+pyodbc://user:pass@terrain_database',
logging_name='terrain',
echo=True)
e2.execute("select 1").fetchall()
}}}
e.g. is there some issue just with the "terrain" database.
also note that we haven't supported the MS ODBC driver for linux as of
yet.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2909#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|