Index: doc/src/sgml/release.sgml =================================================================== RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/release.sgml,v retrieving revision 1.242 diff -c -r1.242 release.sgml *** doc/src/sgml/release.sgml 15 Nov 2003 20:01:11 -0000 1.242 --- doc/src/sgml/release.sgml 16 Nov 2003 00:03:25 -0000 *************** *** 1059,1067 **** Allow cursors outside transactions using WITH HOLD (Neil) In previous releases, cursors were removed at the end of the ! transaction. Using WITH HOLD, the current ! release allows cursors to remain readable after the creating ! transaction. --- 1059,1068 ---- Allow cursors outside transactions using WITH HOLD (Neil) In previous releases, cursors were removed at the end of the ! transaction that created them. Cursors can now be created with ! the WITH HOLD option, which allows them to ! continue to be accessed after the creating transaction has ! committed. *************** *** 1091,1106 **** Properly handle SCROLL with cursors, or report an error (Neil) ! Certain cursors can not be fetched backwards optimally. By ! specifying SCROLL, extra work will be ! performed to guarantee that the cursor can be fetched in reverse ! or random order. ! Implement SQL-compatible option FIRST, LAST, ABSOLUTE n, RELATIVE n for FETCH and MOVE (Tom) --- 1092,1109 ---- Properly handle SCROLL with cursors, or report an error (Neil) ! Allowing random access (both forward and backward scrolling) to ! some kinds of queries cannot be done without some additional ! work. If SCROLL is specified when the cursor ! is created, this additional work will be performed. Furthermore, ! if the cursor has been created with NO SCROLL, ! no random access is allowed. ! Implement SQL-compatible options FIRST, LAST, ABSOLUTE n, RELATIVE n for FETCH and MOVE (Tom) *************** *** 1151,1157 **** Make TRUNCATE transaction-safe (Rod) TRUNCATE can now be used inside a ! transaction, and rolled back if the transaction aborts. --- 1154,1161 ---- Make TRUNCATE transaction-safe (Rod) TRUNCATE can now be used inside a ! transaction. If the transaction aborts, the changes made by the ! TRUNCATE are automatically rolled back.