New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQL_AUTOCOMMIT_ON changes to OFF after calling SET TRANSACTION [ODBC176] #167
Comments
Commented by: Gregori Arjona (garjona) ODBC SQL LOG |
Modified by: Gregori Arjona (garjona)Attachment: SQL_ads.LOG [ 12593 ] |
Commented by: @alexpotapchenko Do you really use ODBC driver 2.0.2 (maybe there are other versions of odbc driver are exist on your computer)? |
Modified by: @alexpotapchenkoAttachment: Firebird ODBC.zip [ 12594 ] |
Modified by: @alexpotapchenkosecurity: Developers [ 10012 ] => |
Commented by: Gregori Arjona (garjona) Hi Alexander. You are wright, this is version 2.0.2.153 and works as you have said, the problem is produced by machines with an older version of ODBC, exactly 2.0.0.148. I did not realize it until you told me. :-( Thanks for all. Regards. |
Modified by: @alexpotapchenkostatus: Open [ 1 ] => Resolved [ 5 ] resolution: Won't Fix [ 2 ] Fix Version: 2.0.3 [ 10581 ] |
Modified by: @alexpotapchenkostatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Gregori Arjona (garjona)
Attachments:
SQL_ads.LOG
Firebird ODBC.zip
By default, after opening a conection and doing some select statement, the odbc driver sets the transaction isolation mode to:
READ COMMITTED NO WAIT NO RECORD_VERSION
I checked this by query to the mon$transaction table.If a do some changes to any table the changes are commited automaticaly.
This mode is not suitable for us, because this blocks reads of changed rows by another computer. But if i change manually the transaction isolation level with the command:
SET TRANSACTION READ WRITE WAIT READ COMMITTED RECORD_VERSION
After doing this i need to commit evey change made on the database, if not commited the changes are lost after closing the connection.
I dont know whats happening but this is driving me nuts, can it be and odbc error?
Thank you.
I send to you an odbc trace file.
The text was updated successfully, but these errors were encountered: