I am having a nightmare of a time getting a single transaction across
multiple tables to work in Borland's Kylix3 with MySQL. It appears that
the Borland driver is saying that the MySQL database only supports a
single active statement per connection.
When I issue an explicit begin transaction, that appears to count as an
active statement. When I then try to issue the update (or insert or
delete) statement, that appears to be the second active command for the
existing connection. Since the Borland driver says the MySQL database
is only allowing a single active command per connection, it clones a new
connection to handle the update statement. Of course, this new
connection knows nothing of the transaction that was begun by the
original connection. This renders transaction support impossible with
Borland's dbExpress and MySQL (even with InnoDB tables).
Is there a way to configure MySQL to report that it will allow multiple
active statements per connection? Otherwise, I'm not sure what to do if
I want to use transactions (a must for my current project). Thanks.
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
[EMAIL PROTECTED]
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
