Open mks26 opened 7 years ago
Savepoints can be supported via the SQL Language; it doesn't seem there is any added value in exposing savepoints through an API.
Might be useful to expose a GetInfo saying whether or not a driver supports (the ANSI SQL syntax for) savepoints, as well as document the interaction and make this usage more discoverable.
Exposing through Getinfo is a good idea, but it will result in again application modification for respective DB. Just a thought.
Providing savepoint API will provide more control to application, as the different DB may have different syntax for savepoint operation and in that case an ODBC application won't achieve interoperability objective. e.g, Oracle and MS SQL server have different syntax for savepoint operations.
Are we planning to place the related documentation for sub-transaction under manual-commit mode?
Hello,
Do we have any plan to support sub-transaction API in ODBC 4.0 specification?
Thanks, Mukesh