--- Phoenix Kiula <[EMAIL PROTECTED]> wrote:
> Isn't this expected behavior? When you update the m2 of the first
> record, it becomes 2 and violates the unique constraint as the second
> row already has an m2 value of 2.
Well, it is a limitation PostgreSQL. This type of update is should work
wi
On Tue, 2007-09-25 at 10:06 +0530, Anoo Sivadasan Pillai wrote:
> But since you can’t control the order, it is likely that the operation
> will sometimes and will succeed sometimes, with the same data.. Weird
> I feel .
Not so weird (IMO). Many databases will return rows unordered unless you
spe
On 25/09/2007, Anoo Sivadasan Pillai <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi,
>
> On further testing I found the same behaviour in Unique keys too, The
> following batch can reproduce the behaviour.
>
> CREATE TABLE master ( m1 INT primary key , m2 int unique ) ;
>
> INSERT INTO master VALUES (
neral@postgresql.org
Subject: Re: [GENERAL] Why the ERROR: duplicate key violates uniqueconstraint
"master_pkey" is raised? - Is this a Bug?
On Mon, 2007-09-24 at 12:50 +0530, Anoo Sivadasan Pillai wrote:
CREATE TABLE master ( m1 INT primary key , m2 VARCHAR(100)) ;
INSERT INTO master V
