All:
Presume:
(1) Multi-user database environment, involving USER1 and USER2
(2) TRANSACT, WAIT and INTERVAL are all properly set
(3) COMMIT commands are strategically and appropriately set within
application code
(4) USER2 woke up in a good mood this morning.
Documentation:
The R:Syntax Transaction Processing documentation addresses a multi-user
scenario in which USER2's command processing is interrupted by USER1's
resource lock:
"While the command is waiting for a lock, you [USER2] are prompted to
continue waiting or to abort."
Questions:
Q#1: If USER2 aborts, does R:BASE automatically perform a ROLLBACK to
the nearest upstream COMMIT in USER2's stack?
Q#2: Say USER2 has elected to abort the locked-out process. How does
R:BASE get USER2 "back into the fight"?
(a) To what point point and state of user-control is USER2 returned
(e.g. a non-frozen "save" button in a Form)?
(b) What information/direction is provided to USER2 until USER1's
resource lock has resolved (e.g. a dialog to the effect: "good time to
get yourself a cuppa, then c'mon back 'n give it a go")?
Thanks much, Bruce
Bruce A. Chitiea | SafeSectors, Inc.
112 Harvard Ave #272 | Claremont CA 91711-4716 | USA
[email protected] | +011 (909) 238-9012 c | +011 (909) 912-8678 f
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/em196bb08a-a039-46f6-8fe5-1d4b3bda0d36%40pathfinder.
