Re: Unique Key Violation 7.0 vs. 6.5.3

> Hi,
> 
> In doing some more 7.0 testing, I ran across a difference in functionality
> concerning unique indexes and errors that are reported when you try to 
> violate the index.  I'm not sure if this change is intentional, so I'm 
> bringing it up here.  In 6.5.3, if you try to update a row that violates 
> a unique index, the query fails and said error is reported to the 
> application.  However, in 7.0 the query succeeds, but updates 0 rows.  Hence, 
> no errors are reported back to the application.    This is not normally 
> a problem because I typically check the constrait before updating.  
> 
> 
> in 7.0/beta3
> basement=>  update foobar set unique_colum = '2000-04-09' where foobar_id = 32;
> UPDATE 0
> basement=> 
> 
> in 6.5.3
> basement=> update foobar set unique_colum = '2000-04-09' where foobar_id = 32;
> ERROR:  Cannot insert a duplicate key into a unique index
> basement=> 

Works here:
test=> insert into kk values (1);INSERT 18740 1test=> insert into kk values (1);ERROR:  Cannot insert a duplicate key
intounique index ii
 

--  Bruce Momjian                        |  http://www.op.net/~candle pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026