Re: delete vs insert vs update due to primary key dups -> which is better - Mailing list pgsql-general

From Michael Glaesemann
Subject Re: delete vs insert vs update due to primary key dups -> which is better
Date
Msg-id 2FA9844F-C3C7-4183-A310-9F7D5C1C1C8C@seespotcode.net
Whole thread Raw
In response to Re: delete vs insert vs update due to primary key dups -> which is better  (Richard Huxton <dev@archonet.com>)
List pgsql-general
On Aug 28, 2007, at 3:10 , Richard Huxton wrote:

> Ow Mun Heng wrote:
>> less typing per insert/update statement so it'll be where a.pkey =
>> b.pkey instead of a.key1 = b.key1 and a.key2 = b.key2
>> and ... up to key5
>
> I'd still leave it alone, but it's your database.

And you can use the row comparison syntax;

WHERE (a.key1, a.key2, a.key3, a.key4, a.key5) = (b.key1, b.key2,
b.key3, b.key4, b.key5)

which I find very convenient as it makes the composite key much
clearer than ANDed equalities.

Michael Glaesemann
grzm seespotcode net



pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: INSERT doc discrepancy
Next
From: "Marcelo de Moraes Serpa"
Date:
Subject: difference between function and stored procedure