We have a multithreaded app written in Clarion 9 (win32), running on several
win 2012 64 bits r2, connecting to Firebird 3 (latest build) via ODBC 32
bits (latest ODBC). We are experiencing a rare propblem, that happens not
very often. The issue is as follows:
The application does not use "begi
On 22/11/2016 12:32, fabia...@itbizolutions.com.au [firebird-support] wrote:
The application does not use "begin transaction and commit", so we let
the
database commit automatically
after a write process, we read the table from another thread inside
the app
or from another app inside the same
SOLVED - Changed code to use explicit transactions and the problem went
away, so I guess implicit transactions was "keeping the transaction opened"
for a few extra milliseconds... while the other "process / thread / or ODBC
object" was trying to read the data added by the last transaction, and a