mirror of https://github.com/postgres/postgres
Move to referential integrity section:
> o Allow DEFERRABLE and end-of-statement UNIQUE constraints? > > This would allow UPDATE tab SET col = col + 1 to work if col has > a unique index. Currently, uniqueness checks are done while the > command is being executed, rather than at the end of the statement > or transaction. > < < * Allow DEFERRABLE and end-of-statement UNIQUE constraints? < < This would allow UPDATE tab SET col = col + 1 to work if col has < a unique index. Currently, uniqueness checks are done while the < command is being executed, rather than at the end of the statement < or transaction.
This commit is contained in:
parent
79222272bb
commit
22bb6929cd
16
doc/TODO
16
doc/TODO
|
@ -2,7 +2,7 @@
|
|||
PostgreSQL TODO List
|
||||
====================
|
||||
Current maintainer: Bruce Momjian (bruce@momjian.us)
|
||||
Last updated: Mon Aug 28 19:20:20 EDT 2006
|
||||
Last updated: Mon Aug 28 19:21:37 EDT 2006
|
||||
|
||||
The most recent version of this document can be viewed at
|
||||
http://www.postgresql.org/docs/faqs.TODO.html.
|
||||
|
@ -683,6 +683,13 @@ SQL Commands
|
|||
http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
|
||||
http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
|
||||
|
||||
o Allow DEFERRABLE and end-of-statement UNIQUE constraints?
|
||||
|
||||
This would allow UPDATE tab SET col = col + 1 to work if col has
|
||||
a unique index. Currently, uniqueness checks are done while the
|
||||
command is being executed, rather than at the end of the statement
|
||||
or transaction.
|
||||
|
||||
|
||||
* Server-Side Languages
|
||||
|
||||
|
@ -873,13 +880,6 @@ Triggers
|
|||
memory. This could exhaust memory for very large trigger queues.
|
||||
This item involves dumping large queues into files.
|
||||
|
||||
* Allow DEFERRABLE and end-of-statement UNIQUE constraints?
|
||||
|
||||
This would allow UPDATE tab SET col = col + 1 to work if col has
|
||||
a unique index. Currently, uniqueness checks are done while the
|
||||
command is being executed, rather than at the end of the statement
|
||||
or transaction.
|
||||
|
||||
* Allow triggers to be disabled in only the current session.
|
||||
|
||||
This is currently possible by starting a multi-statement transaction,
|
||||
|
|
|
@ -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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
|
||||
Last updated: Mon Aug 28 19:20:20 EDT 2006
|
||||
Last updated: Mon Aug 28 19:21:37 EDT 2006
|
||||
</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>.
|
||||
|
@ -618,6 +618,12 @@ first.
|
|||
cascaded tables, seeing the tables in an intermediate state
|
||||
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php</a>
|
||||
<a href="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php</a>
|
||||
</p>
|
||||
</li><li>Allow DEFERRABLE and end-of-statement UNIQUE constraints?
|
||||
<p> This would allow UPDATE tab SET col = col + 1 to work if col has
|
||||
a unique index. Currently, uniqueness checks are done while the
|
||||
command is being executed, rather than at the end of the statement
|
||||
or transaction.
|
||||
</p>
|
||||
</li></ul>
|
||||
</li><li>Server-Side Languages
|
||||
|
@ -793,12 +799,6 @@ first.
|
|||
<p> Right now all deferred trigger information is stored in backend
|
||||
memory. This could exhaust memory for very large trigger queues.
|
||||
This item involves dumping large queues into files.
|
||||
</p>
|
||||
</li><li>Allow DEFERRABLE and end-of-statement UNIQUE constraints?
|
||||
<p> This would allow UPDATE tab SET col = col + 1 to work if col has
|
||||
a unique index. Currently, uniqueness checks are done while the
|
||||
command is being executed, rather than at the end of the statement
|
||||
or transaction.
|
||||
</p>
|
||||
</li><li>Allow triggers to be disabled in only the current session.
|
||||
<p> This is currently possible by starting a multi-statement transaction,
|
||||
|
|
Loading…
Reference in New Issue