 | |
unique constraint on multiple colums does not work
comp.databases.postgresql comp.databases.postgresql
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
unique constraint on multiple colums does not work -
01-21-2008
, 05:27 AM
#2
| |||
| |||
|
|
Hello there, I need to enforce a unique constraint on 2 colums of a table (both of them are not primary keys). I mean that 2 rows are different when at least one of the two above columns is different. The problem is that Postgres enforce the constraint also when only one of the columns is equal to another row, see below the creation code i used for: alter table interfaces add constraint if_uniq unique (name, device); but this constraint raise an error when, for example i try to insert two rows with values: insert into interfaces (name, device) values ('141', 646); insert into interfaces (name, device) values ('141', 637); is this a bug in Postgres? is there a solution? |
us?
CREATE TABLE interfaces
(
<unknown>
CONSTRAINT if_uniq UNIQUE (name, device)
)
;
#3
| |||
| |||
|
|
Hello there, I need to enforce a unique constraint on 2 colums of a table (both of them are not primary keys). I mean that 2 rows are different when at least one of the two above columns is different. The problem is that Postgres enforce the constraint also when only one of the columns is equal to another row, see below the creation code i used for: alter table interfaces add constraint if_uniq unique (name, device); but this constraint raise an error when, for example i try to insert two rows with values: insert into interfaces (name, device) values ('141', 646); insert into interfaces (name, device) values ('141', 637); is this a bug in Postgres? is there a solution? |
us?
CREATE TABLE interfaces
(
<unknown>
CONSTRAINT if_uniq UNIQUE (name, device)
)
;
#4
| |||
| |||
|
|
Hello there, I need to enforce a unique constraint on 2 colums of a table (both of them are not primary keys). I mean that 2 rows are different when at least one of the two above columns is different. The problem is that Postgres enforce the constraint also when only one of the columns is equal to another row, see below the creation code i used for: alter table interfaces add constraint if_uniq unique (name, device); but this constraint raise an error when, for example i try to insert two rows with values: insert into interfaces (name, device) values ('141', 646); insert into interfaces (name, device) values ('141', 637); is this a bug in Postgres? is there a solution? |
us?
CREATE TABLE interfaces
(
<unknown>
CONSTRAINT if_uniq UNIQUE (name, device)
)
;
#5
| |||
| |||
|
|
Hello there, I need to enforce a unique constraint on 2 colums of a table (both of them are not primary keys). I mean that 2 rows are different when at least one of the two above columns is different. The problem is that Postgres enforce the constraint also when only one of the columns is equal to another row, see below the creation code i used for: alter table interfaces add constraint if_uniq unique (name, device); but this constraint raise an error when, for example i try to insert two rows with values: insert into interfaces (name, device) values ('141', 646); insert into interfaces (name, device) values ('141', 637); is this a bug in Postgres? is there a solution? |
us?
CREATE TABLE interfaces
(
<unknown>
CONSTRAINT if_uniq UNIQUE (name, device)
)
;
#6
| |||
| |||
|
|
Hello there, I need to enforce a unique constraint on 2 colums of a table (both of them are not primary keys). I mean that 2 rows are different when at least one of the two above columns is different. The problem is that Postgres enforce the constraint also when only one of the columns is equal to another row, see below the creation code i used for: alter table interfaces add constraint if_uniq unique (name, device); but this constraint raise an error when, for example i try to insert two rows with values: insert into interfaces (name, device) values ('141', 646); insert into interfaces (name, device) values ('141', 637); is this a bug in Postgres? is there a solution? |
us?
CREATE TABLE interfaces
(
<unknown>
CONSTRAINT if_uniq UNIQUE (name, device)
)
;
#7
| |||
| |||
|
|
Hello there, I need to enforce a unique constraint on 2 colums of a table (both of them are not primary keys). I mean that 2 rows are different when at least one of the two above columns is different. The problem is that Postgres enforce the constraint also when only one of the columns is equal to another row, see below the creation code i used for: alter table interfaces add constraint if_uniq unique (name, device); but this constraint raise an error when, for example i try to insert two rows with values: insert into interfaces (name, device) values ('141', 646); insert into interfaces (name, device) values ('141', 637); is this a bug in Postgres? is there a solution? |
us?
CREATE TABLE interfaces
(
<unknown>
CONSTRAINT if_uniq UNIQUE (name, device)
)
;
#8
| |||
| |||
|
|
Hello there, I need to enforce a unique constraint on 2 colums of a table (both of them are not primary keys). I mean that 2 rows are different when at least one of the two above columns is different. The problem is that Postgres enforce the constraint also when only one of the columns is equal to another row, see below the creation code i used for: alter table interfaces add constraint if_uniq unique (name, device); but this constraint raise an error when, for example i try to insert two rows with values: insert into interfaces (name, device) values ('141', 646); insert into interfaces (name, device) values ('141', 637); is this a bug in Postgres? is there a solution? |
us?
CREATE TABLE interfaces
(
<unknown>
CONSTRAINT if_uniq UNIQUE (name, device)
)
;
#9
| |||
| |||
|
|
Hello there, I need to enforce a unique constraint on 2 colums of a table (both of them are not primary keys). I mean that 2 rows are different when at least one of the two above columns is different. The problem is that Postgres enforce the constraint also when only one of the columns is equal to another row, see below the creation code i used for: alter table interfaces add constraint if_uniq unique (name, device); but this constraint raise an error when, for example i try to insert two rows with values: insert into interfaces (name, device) values ('141', 646); insert into interfaces (name, device) values ('141', 637); is this a bug in Postgres? is there a solution? |
us?
CREATE TABLE interfaces
(
<unknown>
CONSTRAINT if_uniq UNIQUE (name, device)
)
;
#10
| |||
| |||
|
|
I need to enforce a unique constraint on 2 colums of a table (both of them are not primary keys). I mean that 2 rows are different when at least one of the two above columns is different. The problem is that Postgres enforce the constraint also when only one of the columns is equal to another row, see below the creation code i used for: alter table interfaces add constraint if_uniq unique (name, device); but this constraint raise an error when, for example i try to insert two rows with values: insert into interfaces (name, device) values ('141', 646); insert into interfaces (name, device) values ('141', 637); is this a bug in Postgres? is there a solution? |
Luuk wrote:
Quote:
|
can you post the definition of your table, so we can see what's <unknown> to us? CREATE TABLE interfaces ( unknown CONSTRAINT if_uniq UNIQUE (name, device) ) ; |
the error message?
--
Lew
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.