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 as it
was not commited yet, the data was not visible. Many many years ago, like 15
years ago, a friend who advised me to use Firebird told me "dont use
explicit transations with Firebird; you'll be better of leaving Firebird
manage it implicit..."; it did not sound correct then.... and it came back
to bite me now...
Cheers,
Fabian
__._,_.___
Posted by: <fabianch@itbizolutions.com.au>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (3) |
Have you tried the highest rated email app?
With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu. Try FAQ and other links from the left-side menu there.
Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu. Try FAQ and other links from the left-side menu there.
Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
.
__,_._,___
No comments:
Post a Comment