Re: Atomicity of UPDATE, interchanging values in unique column

From: daniel alvarez <d-alvarez(at)gmx(dot)de>
To: Rod Taylor <rbt(at)rbt(dot)ca>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Atomicity of UPDATE, interchanging values in unique column
Date: 2003-03-08 21:48:46
Message-ID: 21780.1047160126@www48.gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql


> 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(at)gmx(dot)de>

--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Rod Taylor 2003-03-08 21:56:11 Re: Atomicity of UPDATE, interchanging values in unique
Previous Message Rod Taylor 2003-03-08 21:33:22 Re: Atomicity of UPDATE, interchanging values in unique column