Re: UPDATE OR REPLACE? - Mailing list pgsql-general

From dandl
Subject Re: UPDATE OR REPLACE?
Date
Msg-id 001b01d204ae$2c837900$858a6b00$@andl.org
Whole thread Raw
In response to Re: UPDATE OR REPLACE?  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: UPDATE OR REPLACE?  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
> > In my particular situation the case I care about is when the result
> of an UPDATE is two identical rows. All I really want is a DISTINCT
> option.
>
> Assuming I am following correctly what you want is that the result of
> an UPDATE not be two identical rows.

Correct. In practice I don't care whether the action is IGNORE or REPLACE (in Sqlite terms), the outcome is the same.

Obviously two different records that share the same primary key is a bad thing and worth an error. Two identical
recordsis just boring. 

Regards
David M Bennett FACS

Andl - A New Database Language - andl.org







pgsql-general by date:

Previous
From: Patrick B
Date:
Subject: Re: Rackspace to RDS using DMS (Postgres 9.2)
Next
From: Patrick B
Date:
Subject: 2.5TB Migration from SATA to SSD disks - PostgreSQL 9.2