< 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.
PostgreSQL TODO List
====================
-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.
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
-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
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.
+ 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