E&S CVS Commit: PEAK - SQL transaction semantics have changed. Now, issuing an SQL statement

pje at eby-sarna.com pje at eby-sarna.com
Thu Apr 22 18:33:01 EDT 2004

Module Name:	PEAK
Committed By:	pje
Date:		Thu Apr 22 22:32:23 UTC 2004

Modified Files:
	PEAK/src/peak/storage: SQL.py interfaces.py
	PEAK/src/peak/tools/n2: sql.py

Log Message:
SQL transaction semantics have changed.  Now, issuing an SQL statement
*always* causes the connection to join the active PEAK transaction, even if
you request that the SQL be issued "outside" a transaction.  Such SQL will
be issued outside of the *database* transaction, but not outside of the
PEAK transaction.  This simplifies the overall processing model for dealing
with "untransacted" SQL such as Sybase DDL or read-only Oracle
transactions.  (In particular, the requirement that triggered this change
was to allow Oracle read-only transactions to be released at the end of
the current PEAK transaction.)  Also, got rid of the now-meaningless
'begin' command in n2, and fixed tab completion in n2 to not start a
transaction unintentionally (by making 'listObjects()' methods of
DBs supporting "outside" mode be transaction-agnostic).

To view diffs of this commit, you can use the following URL(s):

To generate a diff of this commit:
cvs rdiff -r1.135 -r1.136 PEAK/CHANGES.txt
cvs rdiff -r1.71 -r1.72 PEAK/src/peak/storage/SQL.py
cvs rdiff -r1.36 -r1.37 PEAK/src/peak/storage/interfaces.py
cvs rdiff -r1.17 -r1.18 PEAK/src/peak/tools/n2/sql.py

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

More information about the source-changes mailing list