Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

SQL Sub queries in check constraint

Can I make SQL sub queries in Check constraint ?

I've a post table with columns id, owner
I've another table action with columns user_id, post_id
Table user with columns id

post_id -> post.id and user_id -> user.id also post.owner -> user.id

Now I want to constraint post(post_id).id != user_id on table action

How is that possible ?

like image 927
Dipro Sen Avatar asked Apr 16 '12 17:04

Dipro Sen


People also ask

Can we use subquery in check constraint?

Sub-queries are not allowed in this context. Only scalar expressions are allowed.

How can check constraint in SQL query?

The syntax for enabling a check constraint in SQL Server (Transact-SQL) is: ALTER TABLE table_name WITH CHECK CHECK CONSTRAINT constraint_name; table_name. The name of the table that you wish to enable the check constraint.

What operators can be used with check constraint?

Check constraints are limited to Boolean operations (e.g., =, >=, <=, or <>), though they may include any SQL2003 predicate, such as IN or LIKE. Check constraints may be appended to one another (when checking a single column) using the AND and OR operators.

Can subqueries be used with DDL statements?

I think create table as ... is the only DDL that will allow "sub-queries".


1 Answers

It is not supported to look beyond the current row in a CHECK constraint.

http://www.postgresql.org/docs/9.1/interactive/sql-createtable.html says:

A check constraint specified as a column constraint should reference that column's value only, while an expression appearing in a table constraint can reference multiple columns.

Currently, CHECK expressions cannot contain subqueries nor refer to variables other than columns of the current row.

There are good reasons for this restriction, but if you like to juggle flaming torches while riding a unicycle through heavy traffic, you can subvert the restriction using functions. The situations in which this will not come back to bite you are rare; you would be much safer to enforce the invariant in trigger code instead.

http://www.postgresql.org/docs/9.1/interactive/triggers.html

like image 197
kgrittn Avatar answered Oct 14 '22 16:10

kgrittn