Move to referential integrity section:

> 	o Allow DEFERRABLE and end-of-statement UNIQUE constraints?
>
> 	  This would allow UPDATE tab SET col = col + 1 to work if col has
> 	  a unique index.  Currently, uniqueness checks are done while the
> 	  command is being executed, rather than at the end of the statement
> 	  or transaction.
>
<
< * Allow DEFERRABLE and end-of-statement UNIQUE constraints?
<
<   This would allow UPDATE tab SET col = col + 1 to work if col has
<   a unique index.  Currently, uniqueness checks are done while the
<   command is being executed, rather than at the end of the statement
<   or transaction.

diff --git a/doc/TODO b/doc/TODO
index a9b86c0b4f2ed2df56742d28c18a4ae83cc1d1cb..a43dc9941594f36f76e8f8444a5c63d77d97dc4a 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Mon Aug 28 19:20:20 EDT 2006
+Last updated:      Mon Aug 28 19:21:37 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -683,6 +683,13 @@ SQL Commands
      http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
      http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
 
+   o Allow DEFERRABLE and end-of-statement UNIQUE constraints?
+
+     This would allow UPDATE tab SET col = col + 1 to work if col has
+     a unique index.  Currently, uniqueness checks are done while the
+     command is being executed, rather than at the end of the statement
+     or transaction.
+
 
 * Server-Side Languages
 
@@ -873,13 +880,6 @@ Triggers
   memory.  This could exhaust memory for very large trigger queues.
   This item involves dumping large queues into files.
 
-* Allow DEFERRABLE and end-of-statement UNIQUE constraints?
-
-  This would allow UPDATE tab SET col = col + 1 to work if col has
-  a unique index.  Currently, uniqueness checks are done while the
-  command is being executed, rather than at the end of the statement
-  or transaction.
-
 * Allow triggers to be disabled in only the current session.
 
   This is currently possible by starting a multi-statement transaction,

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index eee26db97b6a35b72361793b0f0f9798c073739b..cfce3943af68adb5d4095adbce30c1f398bf1e59 100644 (file)
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 
 PostgreSQL TODO List
 Current maintainer:     Bruce Momjian ([email protected])
-Last updated:           Mon Aug 28 19:20:20 EDT 2006
+Last updated:           Mon Aug 28 19:21:37 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -618,6 +618,12 @@ first.
           cascaded tables, seeing the tables in an intermediate state
           http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
           http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
+
+    Allow DEFERRABLE and end-of-statement UNIQUE constraints?
+          This would allow UPDATE tab SET col = col + 1 to work if col has
+          a unique index.  Currently, uniqueness checks are done while the
+          command is being executed, rather than at the end of the statement
+          or transaction.
 
   
   Server-Side Languages
@@ -793,12 +799,6 @@ first.
   Right now all deferred trigger information is stored in backend
   memory.  This could exhaust memory for very large trigger queues.
   This item involves dumping large queues into files.
-
-  Allow DEFERRABLE and end-of-statement UNIQUE constraints?
-  This would allow UPDATE tab SET col = col + 1 to work if col has
-  a unique index.  Currently, uniqueness checks are done while the
-  command is being executed, rather than at the end of the statement
-  or transaction.
 
   Allow triggers to be disabled in only the current session.
   This is currently possible by starting a multi-statement transaction,