On Sat, Jan 10, 2009 at 9:54 PM, Michael Trier mtr...@gmail.com wrote:
1. Override do_begin so that it creates a cursor and then executes on the
cursor:
def do_begin(self, connection):
cursor = connection.cursor()
cursor.execute(SET IMPLICIT_TRANSACTIONS OFF)
This has been corrected in http://www.sqlalchemy.org/trac/changeset/5641
. I actually did both things, since using the cursor is the right
thing to do.
Thats awesome, thanks so much for your time and help with this!
TH
--~--~-~--~~~---~--~~
You received
1. Override do_begin so that it creates a cursor and then executes on the
cursor:
def do_begin(self, connection):
cursor = connection.cursor()
cursor.execute(SET IMPLICIT_TRANSACTIONS OFF)
cursor.execute(BEGIN TRANSACTION)
this would be appropriate since
Hi,
On Fri, Jan 9, 2009 at 12:45 PM, t...@twopeasinabucket.com
t...@twopeasinabucket.com wrote:
On Jan 7, 10:41 pm, Michael Trier mtr...@gmail.com wrote:
Hi,
On Wed, Jan 7, 2009 at 10:43 PM, Jaimy Azle jaimy.a...@gmail.com
wrote:
Hi,
it seems mssql wrapper for pymmsql DBAPI
Thanks Michael, I appreciate it.
As mentioned previously, pymssql support is no where near the level
of support as pyodbc. In addition the maintainer has not updated
this library for several years. Finally, Microsoft warns against
it's use going forward, When writing new applications,
Hi,
On Wed, Jan 7, 2009 at 10:43 PM, Jaimy Azle jaimy.a...@gmail.com wrote:
Hi,
it seems mssql wrapper for pymmsql DBAPI driver in sqlalchemy 0.5.0
(release) is broken. I haven't check it out with adodbapi, but
pyodbc confirmed works.
Thanks for the test. I will look at this tomorrow.
