From: daniel alvarez <d-alvarez@gmx.de>
To: Rod Taylor <rbt@rbt.ca>
Cc: pgsql-sql@postgresql.org
Subject: Re: Atomicity of UPDATE, interchanging values in unique column
Date: Sat, 8 Mar 2003 22:48:46 +0100 (MET)
Message-ID: <21780.1047160126@www48.gmx.net> (raw)
References: <1047159202.28251.196.camel@jester>
> The first is what you want. PostgreSQL needs some work in the
> evaluation of unique indexes to properly support it.
>
> Namely, when it sees a conflict when inserting into the index, it needs
> to record the fact, and revisit the conflict at the end of the command.
> Lots of work...
OK. The long-term goal would then be to get rid of such oddities. But what
can I do right now as a user to solve that issue for my application?
There must be a better solution than the additional dummy update.
Any ideas?
Daniel Alvarez Arribas <d-alvarez@gmx.de>
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: d-alvarez@gmx.de, rbt@rbt.ca
Subject: Re: Atomicity of UPDATE, interchanging values in unique column
In-Reply-To: <21780.1047160126@www48.gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox