Re: Transaction Problems

Christer,

That makes sense why I could not get it to work ;-) while SQL Server would
effectively rollback the txn.

Thanks for the education. Now comes the real question...

If I want txns and MySQL using MyODBC I will just have to roll it by hand
then? Any other ways that people have done this? Or other methods to connect
to MySQL?

Thanks again, I really appreciate it.
Frank

----- Original Message ----- 
From: "Christer Ljung" <christer@xxxxxxxxxxxx>
To: <myodbc@xxxxxxxxxxxxxxx>
Sent: Wednesday, March 10, 2004 5:26 PM
Subject: RE: Transaction Problems



The SQLTransact and SQLEndTrans APIs are there to support standard
transactions on your DBMS through the ODBC driver, like in a basic
2-tier app where client is submitting transactions. Under MTS/COM+ it's
a completely different ballgame. The TX-management is actually
surpressed since it is MTS/COM+ that has the final vote. It must be so
since multiple Resource Managers (ie MySQL + SQL Server) might be
enrolled in the same distributed transaction, which is in the scope of
DTC/MTS/COM+. The transact.c file just translates api calls into SQL
statements like BEGIN/COMMIT/ROLLBACK that are submitted to MySQL. For
DTC/MTS/COM+ transaction support, the ODBC api SQLSetConnectAttr must
handle the attribute SQL_COPT_SS_ENLIST_IN_DTC - and in transact.c, it
doesn't.

Christer


-----Original Message-----
From: Frank Febbraro [mailto:frankfebbraro@xxxxxxxxxxxxx]
Sent: den 10 mars 2004 22:56
To: myodbc@xxxxxxxxxxxxxxx
Subject: Re: Transaction Problems

Well not sure in too much detail, but in looking at the source code
there is a file called transact.c that seems to implement both
SQLTransact and SQLEndTrans which are old and new versions of the
commit/rollback ODBC functions. I kinda figured if it implemented these
then it was probably setup to support the transactions.  Not sure how
this comes into play with MTS/DTC stuff though.

Again I dont know too much and could be completely missing something.

----- Original Message -----
From: "Christer Ljung" <christer@xxxxxxxxxxxx>
To: <myodbc@xxxxxxxxxxxxxxx>
Sent: Wednesday, March 10, 2004 4:38 PM
Subject: RE: Transaction Problems


Are you sure that this is supported?

For this to work, it would require support for MS DTC Transactions, ie
that the MyODBC driver can act as a Resource Dispenser under MTS/COM+
and that the MySQL database server can act as a Resource Manager. Never
thought of this myself but a really quick glance through the MyODBC
sources tells me that this is not supported (but I might be wrong).

Christer


________________________________

From: Frank Febbraro [mailto:frankfebbraro@xxxxxxxxxxxxx]
Sent: den 10 mars 2004 00:52
To: myodbc
Subject: Transaction Problems


I am using MyODBC 3.51 on Windows XP Professional talking to a MySQL
4.0.x DB on a Windows 2000 Server.

Using C#  ServicedComponents ([Transaction] and [AutoComplete]) for
transaction support and the System.Data.Odbc package.

I can get SQL Server (via the ODBC layer) to rollback transactions, but
the same code using MySQL (via ODBC) does not seem to behave similarly.
I switched to the debugging DLL and I do not see any
BEGIN/COMMIT/ROLLBACK statements beign dumped into myodbc.sql. I do
however see "set autocommit=0;" in the myodbc.log file.

Can someone help me get to the bottom of this?

I have attached the my.ini file if that helps.

Thanks so much,
Frank





-- 
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:
http://lists.mysql.com/myodbc?unsub=christer@xxxxxxxxxxxx



-- 
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:
http://lists.mysql.com/myodbc?unsub=frankfebbraro@xxxxxxxxxxxxx



-- 
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@xxxxxxxxxxx