database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-14 18:42:34 +03:00
Code Activity

Update MERGE:

Browse Source 
>
>   To implement this cleanly requires that the table have a unique index
>   so duplicate checking can be easily performed.
>
This commit is contained in:
Bruce Momjian
2005-11-15 23:08:24 +00:00
parent 788f7c63a1
commit 698ee9c3e7
2 changed files with 9 additions and 2 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: Thu Oct 27 10:15:56 EDT 2005
Last updated: Tue Nov 15 18:08:23 EST 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -371,6 +371,10 @@ SQL Commands
* Add a GUC variable to warn about non-standard SQL usage in queries
* Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
triggers?)
To implement this cleanly requires that the table have a unique index
so duplicate checking can be easily performed.
* Add NOVICE output level for helpful messages like automatic sequence/index
creation
* %Add COMMENT ON for all cluster global objects (roles, databases

5
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: Thu Oct 27 10:15:56 EDT 2005
Last updated: Tue Nov 15 18:08:23 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>.
@ -341,6 +341,9 @@ first.
</li><li>Add a GUC variable to warn about non-standard SQL usage in queries
</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.
</p>
</li><li>Add NOVICE output level for helpful messages like automatic sequence/index
creation
</li><li>%Add COMMENT ON for all cluster global objects (roles, databases