database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-03 09:13:20 +03:00
Code Activity

Update, add mention of user locking table before MERGE:

Browse Source 
<   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.
This commit is contained in:
Bruce Momjian
2005-11-16 18:45:09 +00:00
parent ccdcd19672
commit 84bb3876bc
2 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/TODO
View File

@@ -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

6
doc/src/FAQ/TODO.html
View File

@@ -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