Update, add mention of user locking table before MERGE:

< so duplicate checking can be easily performed. > so duplicate checking can be easily performed. It is possible to > do it without a unique index if we require the user to LOCK the table > before the MERGE.

Update, add mention of user locking table before MERGE:
< so duplicate checking can be easily performed. > so duplicate checking can be easily performed. It is possible to > do it without a unique index if we require the user to LOCK the table > before the MERGE.
84bb3876 · Bruce Momjian · ccdcd196 · 84bb3876 · 84bb3876
Commit 84bb3876 authored Nov 16, 2005 by Bruce Momjian
Hide whitespace changes
Inline Side-by-side

Showing with 8 additions and 4 deletions

doc/TODO doc/TODO +4 -2

doc/src/FAQ/TODO.html doc/src/FAQ/TODO.html +4 -2

No files found.
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:	Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated:		Wed Nov 16 11:33:25 EST 2005
+Last updated:		Wed Nov 16 13:44:51 EST 2005

 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -373,7 +373,9 @@ SQL Commands
  triggers?)

  To implement this cleanly requires that the table have a unique index
-  so duplicate checking can be easily performed.
+  so duplicate checking can be easily performed.  It is possible to
+  do it without a unique index if we require the user to LOCK the table
+  before the MERGE.

 * Add NOVICE output level for helpful messages like automatic sequence/index
  creation

--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
 <h1><a name="section_1">PostgreSQL TODO List</a></h1>
 <p>Current maintainer:     Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated:           Wed Nov 16 11:33:25 EST 2005
+Last updated:           Wed Nov 16 13:44:51 EST 2005
 </p>
 <p>The most recent version of this document can be viewed at<br/>
 <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -342,7 +342,9 @@ first.
  </li><li>Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
  triggers?)
 <p>  To implement this cleanly requires that the table have a unique index
-  so duplicate checking can be easily performed.
+  so duplicate checking can be easily performed.  It is possible to
+  do it without a unique index if we require the user to LOCK the table
+  before the MERGE.
 </p>
  </li><li>Add NOVICE output level for helpful messages like automatic sequence/index
  creation