Turning off Autocommit & "driver not capable" error 1

[GaryAshford]

Any programmers out there? )
Assuming that transactions are supported in MySQL version 3.23.38, how is it that when my ODBC application does
SQLSetConnectOption(..,SQL_AUTOCOMMIT,false)
the call fails with error message; "Driver not capable" ?

SQLGetInfo(..,SQL_TXN_CAPABLE,..) returns SQL_TC_DDL_COMMIT
which would indicate that transactions are (should be) supported(?)

Is this a bug with the version 3.51.05 MyODBC driver, maybe I have the wrong version of MySQL or do I have to do something to the database to turn transactions "on"?
Many thanks

 

[sleipnir214]

What is the type of table you are using? Transactions are only available under MySQL when you are using the InnoDB table type. Want the best answers? Ask the best questions:

http://www.catb.org/~esr/faqs/smart-questions.html

TANSTAAFL!

 

[GaryAshford]

Thanks for your reply.
I'm not trying to use any tables just yet.
I am trying to tell MySQL what I want the transaction mode to be once I have logged on, i.e. manual transaction mode.
Can this be done at the connection level?
Maybe I have to have one or more innoDB tables before this will work?

 

[sleipnir214]

Since in MySQL transactions have meaning only in the context of operations on an InnoDB table, I doubt you can perform transaction tuning at the connection level. Want the best answers? Ask the best questions:

http://www.catb.org/~esr/faqs/smart-questions.html

TANSTAAFL!

 

[GaryAshford]

Thanks, this is great.
So I guess it would be true to say that whilst innoDB tables support transactions, the API call; SQLSetConnectOption( SQL_AUTOCOMMIT, on/off) is not supported by MySQL.

 

[sleipnir214]

Probably.

But whose API are you calling? Want the best answers? Ask the best questions:

http://www.catb.org/~esr/faqs/smart-questions.html

TANSTAAFL!

 

[GaryAshford]

Ah- good question.
I am using an iMac running MacOS9.2.2 talking via Openlink's Generic ODBC driver and the iODBC Driver Manager to a Win2k DataDirect ODBC datasource at the other end which is talking to MySQL running on a Linux box!
So I guess I am using Openlink's ODBC API. I seem to remember getting the same error when I used Merant's 3.51 Driver Manager.

(How am I doing this? - Check out

http://www.omnis.net)

 

[sleipnir214]

With all those levels of indirection between you can the database, were I you, I'd be happy if I could talk to the server at all! Want the best answers? Ask the best questions:

http://www.catb.org/~esr/faqs/smart-questions.html

TANSTAAFL!