mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add MERGE TODO.detail:

Browse Source 
>   [merge]
378a380
>   [merge]
This commit is contained in:
Bruce Momjian 2005-12-01 22:12:35 +00:00
parent f28bdd95c1
commit 915fb7f687
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/TODO
View File

@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Thu Dec 1 17:07:44 EST 2005 Last updated: Thu Dec 1 17:12:27 EST 2005
The most recent version of this document can be viewed at The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
@ -370,12 +370,14 @@ SQL Commands
* Add a GUC variable to warn about non-standard SQL usage in queries * Add a GUC variable to warn about non-standard SQL usage in queries
* Add SQL-standard MERGE command, typically used to merge two tables * Add SQL-standard MERGE command, typically used to merge two tables
[merge]
This is similar to UPDATE, then for unmatched rows, INSERT. This is similar to UPDATE, then for unmatched rows, INSERT.
Whether concurrent access allows modifications which could cause Whether concurrent access allows modifications which could cause
row loss is implementation independent. row loss is implementation independent.
* Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT * Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT
[merge]
To implement this cleanly requires that the table have a unique index To implement this cleanly requires that the table have a unique index
so duplicate checking can be easily performed. It is possible to so duplicate checking can be easily performed. It is possible to

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

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <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/> <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Thu Dec 1 17:07:44 EST 2005 Last updated: Thu Dec 1 17:12:27 EST 2005
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <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>. <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@ -340,11 +340,13 @@ first.
</p> </p>
</li><li>Add a GUC variable to warn about non-standard SQL usage in queries </li><li>Add a GUC variable to warn about non-standard SQL usage in queries
</li><li>Add SQL-standard MERGE command, typically used to merge two tables </li><li>Add SQL-standard MERGE command, typically used to merge two tables
[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?merge">merge</a>]
<p> This is similar to UPDATE, then for unmatched rows, INSERT. <p> This is similar to UPDATE, then for unmatched rows, INSERT.
Whether concurrent access allows modifications which could cause Whether concurrent access allows modifications which could cause
row loss is implementation independent. row loss is implementation independent.
</p> </p>
</li><li>Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT </li><li>Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT
[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?merge">merge</a>]
<p> To implement this cleanly requires that the table have a unique index <p> To implement this cleanly requires that the table have a unique index
so duplicate checking can be easily performed. It is possible to 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 do it without a unique index if we require the user to LOCK the table