Hmmm. A "read commited" property would be nice. Otherwise, consider
this:
Table A has a column "X" (primary key). Autocommit is OFF.
Client 1: update ... set X=3 where X=9;
Client 2: select... where X=9: Result: zero rows.
Client 2: insert... X=9; Commit -- success? Or will it fail?
Client 1: Rollback.... whoops... two rows with X=9? Or will the
rollback fail?
Cheers,
Frank+++
Am 06.12.2006 um 01:59 schrieb Charles Yeomans:
That's two transactions. I want to be able to roll back. I wrote
some test code that suggests that transactions work the way I
expect them to.
Charles Yeomans
On Dec 5, 2006, at 7:27 PM, Tom Benson wrote:
Or you can
UPDATE
COMMIT
SELECT
UPDATE
COMMIT
- Tom
On 06/12/2006, at 9:54 AM, Carlos M wrote:
On Dec 05, 2006 8:58 PM, Charles Yeomans wrote:
Suppose I have a REALSQLDatabase transaction having the
following form.
UPDATE
SELECT
UPDATE
COMMIT
Should the SELECT statement see the effect of the UPDATE statement?
It seems like it should.
...
--
Günter Schmidt & Co. oHG
Frank Bitterlich eMail: [EMAIL PROTECTED]
Ben-Gurion-Ring 21 WWW: http://www.gsco.de/
D-60437 Frankfurt Tel.: 069 / 156809-29
GERMANY Fax: 069 / 156809-28
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
