[Subversion] / PEAK / CHANGES.txt  

Revision 1738


Jump to revision:
Previous Next
Author: pje
Date: Thu Apr 22 22:32:23 2004 UTC (19 years, 11 months ago)

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).

Changed paths:

Path Action Text Changes Prop Changes Diff to Previous
PEAK/CHANGES.txt modified X   (diff to previous)
PEAK/src/peak/storage/SQL.py modified X   (diff to previous)
PEAK/src/peak/storage/interfaces.py modified X   (diff to previous)
PEAK/src/peak/tools/n2/sql.py modified X   (diff to previous)

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help