Subject | any zeos/fb/lazarus users here that can verify transaction behavior |
---|---|
Author | |
Post date | 2015-09-27T18:22:33Z |
Hi-
I am using zeosdbo-7.1.4, fb 2.5 without the extra "d", and lazarus v1.4.2.
I have a similar thread posted in lazarus db forum but it looks like it might go unanswered.
I will try to keep this short as possible.
in isql I can make this work with two isql-fb open:
set transaction read write isolation level read committed no record_version wait.
post pending update to record 1 in console 1.
set transaction read write isolation level read committed no record_version wait.
post pending update to record 1 in console 2
go to console 1 and commit change to record 1
go back to console 2 and commit change to record 1
per Helen's book on volume 2 p. 196 (Transactions) this behavior that works in isql-fb doesn't seem to behaving this way in lazarus with zeos and fb. I am using zconnection. I like it better than sqldb because it has more options in the gui and doesn't complain when I put in for the db "employee (alias)".
I drop it down to one isql-fb in console mode (lower TID) and reset zconnection, set options, and then reconnect and activate my zquery (higher TID).
Can anyone check this or have you noticed similar?
Both read committed (record version) and snapshot seem to work otherwise.
if I can get past this question I will know 3 different different types of transactions for my hobby project I will start soon.
Thx! - jim
I am using zeosdbo-7.1.4, fb 2.5 without the extra "d", and lazarus v1.4.2.
I have a similar thread posted in lazarus db forum but it looks like it might go unanswered.
I will try to keep this short as possible.
in isql I can make this work with two isql-fb open:
set transaction read write isolation level read committed no record_version wait.
post pending update to record 1 in console 1.
set transaction read write isolation level read committed no record_version wait.
post pending update to record 1 in console 2
go to console 1 and commit change to record 1
go back to console 2 and commit change to record 1
per Helen's book on volume 2 p. 196 (Transactions) this behavior that works in isql-fb doesn't seem to behaving this way in lazarus with zeos and fb. I am using zconnection. I like it better than sqldb because it has more options in the gui and doesn't complain when I put in for the db "employee (alias)".
I drop it down to one isql-fb in console mode (lower TID) and reset zconnection, set options, and then reconnect and activate my zquery (higher TID).
Can anyone check this or have you noticed similar?
Both read committed (record version) and snapshot seem to work otherwise.
if I can get past this question I will know 3 different different types of transactions for my hobby project I will start soon.
Thx! - jim