Batch TransactionNote that the [III - Batch Transaction] described in the above thread is for simple OLTP systems, that already have proper ACID Transactions. Whereas the [Batch Transaction] defined in the link below is for coding the equivalent of CASCADE, which is an infantile, fantasy concept that is not permitted on commercial SQL platforms. Thius code provides the proper method to move the entire tree from OldKey to NewKey.
Nicola
In the /Stored Proc for OLTP Transactions/ thread, you posed questions
re "Serialisation" and "Schedules", which I found very odd:
- why on earth should a developer or a DBA be concerned about such
things (internal operation of the server) ?
- a Schedule implies single-threaded operation (we have been fully multi-threaded since 1975, not to mention Sybase is massively so at
all levels)
I found this, it appears it is being taught at Berkeley, as rCLcomputer sciencerCY about rCLdatabasesrCY. Why, for what purpose ???
https://dsf.berkeley.edu/dbcourse/lecs/22cc.pdf
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 10:49:26 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
3 files (7,546K bytes) |
| Messages: | 265,193 |