Re: How to create unique constraint on NULL columns
От | Andrus |
---|---|
Тема | Re: How to create unique constraint on NULL columns |
Дата | |
Msg-id | db8kk9$27nv$1@news.hub.org обсуждение исходный текст |
Ответ на | How to create unique constraint on NULL columns ("Andrus" <eetasoft@online.ee>) |
Ответы |
Re: How to create unique constraint on NULL columns
Re: How to create unique constraint on NULL columns |
Список | pgsql-general |
>> How to create constraint so that NULL values are treated equal and second >> insert is rejected ? > > Rethink your data design --- this behavior is required by the SQL > standard. I have a table of users permissions by departments CREATE TABLE permission ( id serial, user_id CHAR(10) NOT NULL REFERENCES user, permission_id CHAR(10) NOT NULL REFERENCES privilege, department_id CHAR(10) REFERENCES department , UNIQUE ( user_id, permission_id, department_id ) ) permission_id is a permission name: Invoice, Waybill etc. department _id is a code of department whose documents user is authorized to access. if department _id is NULL, user has access to all departments data. By this design it is meaningless to have two records with same user_id and permission_id both having department_id NULL So I want that Postgres does not allow to insert them. How I should rethink this data design to be implemented in CREATE TABLE statement ? Andrus.
В списке pgsql-general по дате отправления: