mirror of
https://github.com/postgres/postgres.git
synced 2025-07-31 22:04:40 +03:00
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.
This commit is contained in:
6
doc/TODO
6
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
|
||||
|
Reference in New Issue
Block a user