ср, 19 сент. 2018 г. в 19:57, Gabor Boros :
> Default value of ReadConsistency is illogical for me. The
> documentation say "To help test existing applications...". If I want to
> test a new feature I turn it on. Currently turn off to eliminate "update
> conflicts...". (My own test application exec
2018. 09. 03. 10:53 keltezéssel, Vlad Khorsun írta:
Issue (a) is fixed now (see above) but issue (b) is hard to fix and i
need some time
to find if it can be fixed and how to do it. Probably, it should not be
fixed
at all (hi, Adriano ;)). I going to try this test with execute
statement, jus
31.08.2018 22:23, Gabor Boros wrote:
Hi All,
Now (with 4.0.0.1190) works with one (ISQL) client but got "update conflicts with concurrent update" immediately with two or more
clients.
This is because i fixed handling of request snapshot in autonomous
transactions.
Thank to your message.
Hi All,
Now (with 4.0.0.1190) works with one (ISQL) client but got "update
conflicts with concurrent update" immediately with two or more clients.
Gabor
2018. 08. 23. 17:22 keltezéssel, Gabor Boros írta:
Hi All,
I tried Thomas' test case (see the link below) with the actual snapshot
of 4.0
Hi All,
I tried Thomas' test case (see the link below) with the actual snapshot
of 4.0 (4.0.0.1170 SS Win32) and got the next error instantly with one
ISQL session. No problem with multiple (5) ISQL sessions if set
ReadConsistency to 0. Why the engine not wait for concurrent
transactions? I a
