Currently the ODBC DA doesn't handle transactions to Level3 and therefore is a major performance bottleneck on my sites. The reasoning for it not going to level 3 I believe is because the ODBC spec doesn't state whether it is thread safe or not. Surely some ODBC implementations must be thread safe. If anyone knows which ones are could they say and then maybe we could have an option in the ODBCDA to which level of transaction support we use.
On 11/3/99 7:24 PM, Jay, Dylan at djay@lucent.com wrote:
Currently the ODBC DA doesn't handle transactions to Level3 and therefore is a major performance bottleneck on my sites. The reasoning for it not going to level 3 I believe is because the ODBC spec doesn't state whether it is thread safe or not. Surely some ODBC implementations must be thread safe. If anyone knows which ones are could they say and then maybe we could have an option in the ODBCDA to which level of transaction support we use.
That's not why :-) THe reason is that our approach to implementation was flawed for thread-safety. We are currently undertaking a new X/Open CLI interface that will work with all libraries compatible with that---including ODBC. Thread safety will be a check box, rather than automatic decision. Chris -- | Christopher Petrilli Python Powered Digital Creations, Inc. | petrilli@digicool.com http://www.digicool.com
participants (2)
-
Christopher Petrilli -
Jay, Dylan