CHECK constraint question

Oracle 11 R2

My question is if I can create a check constraint using a SELECT statement on a different table?

So instead of

CHECK (building ('01', ' 02', ' 03'));

I can do something like this:

CHECK (select distinct from the other table);

Example of welcome.

user10480146 wrote:
I'm just checking if the building is in the other table. Is a foreign key must use the same columns as the primary key? Or I can use a foreign key with ALL the columns from the other table?

A unique key will do.

Tags: Database

Similar Questions

Get a NAMED check constraint when the entity attribute derived from the field
I'm designing a new database and beginning with a logic model of the ER. I've defined several areas, such as the NO_YES field (with values of ' no and 'Y'). When I use this area as a data type of an attribute of the entity (for example, the CHANGE_REQUEST.IS_APPROVED attribute), I also specify a constraint name (for example, CR_APPROVED_CK) of the attribute (this is done in the Group of constraint, property name constraint and the properties of the attribute dialog box, default value).

When I have the logic model to a relational model of the engineer, the constraint name is lost. Specifically, for the definition of the table that is created, for the column in question, in the default column properties and constraints Panel dialog box, the name of constraint property is empty. When I generated the DDL of the relational model, the check constraint that is generated is an inline check constraint (such as ' IS_APPROVED VARCHAR2 (1) CHECK (IS_APPROVED IN ('n', 'Y')) '). When this DDL is executed to generate database objects, the created check constraint has a system-generated name. I want the constraint to have a name that I create.

By experimentation, I found that in the relational model, if I specify a value for the property name of the constraint in the DOF resulting constraint get named (an ALTER TABLE statement is generated that contains "ADD CONSTRAINT CR_APPROVED_CK CHECK (IS_APPROVED IN ('n', 'Y'))"). However, I have redundantly change the relational model in the same way that I edited the logic model to specify the constraint names.

Is there a way to guarantee that the constraint names defined in a logic model transferred during the engineering of a logic model to a physical model.

The version of the Data Modeler I use is 3.0.0.665.
Is there a way to guarantee that the constraint names defined in a logic model transferred during the engineering of a logic model to a physical model.

There is ' compare/copy options' tab in the technical dialogue - clear the checkbox "do not apply to new objects.

Philippe

Distinguish NOT NULL constraints Check constraints

Join user_constraints to user_cons_columns for constraint_type = 'C' indicates the Check constraints, and NOT NULL constraints, but also (because those are implemented as Check constraints).

My question is how to filter constraints NOT NULL to let only the 'normal Check constraints '?

I tried WHERE SUBSTR(search_condition,-12,12) & LT; & GT; 'IS NOT NULL '.
but as search_condition is of type LONG, I can't use substring.

Has anyone already found it? Thank you!!

ByronBarton wrote:

Has anyone already found it?

Well, there is no easy way. Simple, if you always create named* validation constraints. If so, online NOT NULL constraint will get name generated and forced check no:

SQL> create table test_tbl(
  2                        c1 number not null,
  3                        c2 number,
  4                        constraint test_tbl_chk1
  5                          check(
  6                                c2 is not null
  7                               )
  8                       )
  9  /

Table created.

SQL> select  constraint_name,
  2          generated
  3    from  user_constraints
  4    where table_name = 'TEST_TBL'
  5  /

CONSTRAINT_NAME                GENERATED
------------------------------ --------------
SYS_C008666                    GENERATED NAME
TEST_TBL_CHK1                  USER NAME

SQL>

However, if the check constraint is not named we:

SQL> create table test_tbl(
  2                        c1 number not null,
  3                        c2 number,
  4                        check(
  5                              c2 is not null
  6                             )
  7                       )
  8  /

Table created.

SQL> select  constraint_name,
  2          generated
  3    from  user_constraints
  4    where table_name = 'TEST_TBL'
  5  /

CONSTRAINT_NAME                GENERATED
------------------------------ --------------
SYS_C008668                    GENERATED NAME
SYS_C008669                    GENERATED NAME

SQL>

Then, the only way I know is:

SQL> column owner format a10
SQL> column table_name format a10
SQL> column column_name format a10
SQL> select  u.name owner,
  2          t.name table_name,
  3          a.name column_name,
  4          c.name constraint_name,
  5          decode(k.type#,7,'NOT NULL',1,'CHECK CONSTRAINT','UNKNOWN') type
  6    from  sys.USER$ u,
  7          sys.CON$  c,
  8          sys.CDEF$ k,
  9          sys.OBJ$ t,
 10          sys.COL$ a,
 11          sys.CCOL$ r
 12    where u.name   = user
 13      and c.owner# = u.user#
 14      and k.con#   = c.con#
 15      and t.obj#   = k.obj#
 16      and t.name   = 'TEST_TBL'
 17      and a.obj#   = t.obj#
 18      and r.col#   = a.col#
 19      and r.con#   = k.con#
 20      and r.obj# = k.obj#
 21  /

OWNER      TABLE_NAME COLUMN_NAM CONSTRAINT_NAME                TYPE
---------- ---------- ---------- ------------------------------ ----------------
SCOTT      TEST_TBL   C1         SYS_C008668                    NOT NULL
SCOTT      TEST_TBL   C2         SYS_C008669                    CHECK CONSTRAINT

SQL>

SY.

problem with check constraint

Hi, could someone help me solve a problem with the check constraint.
CREATE TABLE RMD_2
(
NUMBER (10,0) "RMD_ID."
"ABB" VARCHAR2 (16 BYTE),
"act_ind CHAR (1 BYTE)
)
ALTER TABLE SYSADM. CONTRACT_DATA_EXCHANGE ADD CONSTRAINT 'RMD_2_C1 '.
CHECK)
act_ind IN('P','T',)
)
SQL > insert
2 in rmd_2
3 values(1,'A','X')
4.
Insert
*
ERROR on line 1:
ORA-02290: check constraint (RMD_2_C1) violated
SQL > insert
2 in rmd_2
3 values(1,'A','N')
4.
1 line of creation.
SQL > insert
2 in rmd_2
3 values(1,'A',)
4.
1 line of creation.
SQL > insert
so I don't understand why the N value is accepted

User235910 wrote:

Hi, could someone help me solve a problem with the check constraint.

CREATE TABLE RMD_2

(

NUMBER (10,0) "RMD_ID."

"ABB" VARCHAR2 (16 BYTE),

"act_ind CHAR (1 BYTE)

)

ALTER TABLE SYSADM. CONTRACT_DATA_EXCHANGE ADD CONSTRAINT 'RMD_2_C1 '.

CHECK)

act_ind IN('P','T',)

)

SQL > insert

2 in rmd_2

3 values(1,'A','X')

4.

Insert

*

ERROR on line 1:

ORA-02290: check constraint (RMD_2_C1) violated

SQL > insert

2 in rmd_2

3 values(1,'A','N')

4.

1 line of creation.

SQL > insert

2 in rmd_2

3 values(1,'A',)

4.

1 line of creation.

SQL > insert

so I don't understand why the N value is accepted

the posted CONSTRAINT is not on the table RMD_2, but on table SYSADM. CONTRACT_DATA_EXCHANGE

Issue by creating the Check constraint

Hi Experts,
I have obligation to create a check on a column constraint (Number (6.2)) is where in the max value must be less than 4000.
But the column already has the data of more than 4000. Also, I can't delete the data that is already present in the table.
I'm just using an alter command
SQL > alter table test add check constraint CC_A (an < 4000);
Error is:
SQL error: ORA-02293: cannot validate (CC_A) - violated check constraint
02293 00000 - "can't validate (s.%s) - violated check constraint.
* Cause: an alter table operation tried to validate a check constraint to
populated table that has nocomplying values.
Can you suggest me work around him?
Kind regards
RV

Hello

RV says:

Hi Experts,

I have obligation to create a check on a column constraint (Number (6.2)) is where in the max value must be less than 4000.

But the column already has the data of more than 4000. Also, I can't delete the data that is already present in the table.

I'm just using an alter command

SQL > alter table test add constraint CC_A (one check<>

Error is:

SQL error: ORA-02293: cannot validate (CC_A) - violated check constraint

02293 00000 - "can't validate (s.%s) - violated check constraint.

* Cause: an alter table operation tried to validate a check constraint to

populated table that has nocomplying values.

Can you suggest me work around him?

Kind regards

RV

You can specify NOVALIDATE ACTIVATE when you create the constraint.

ALTER TABLE test

ADD CONSTRAINT cc_a CHECK (one<>

ENABLE NOVALIDATE

;

The constraint does not apply to the values already in the table, but if you update a column where the condition is violated, the constraint applies to the new value.

Customized using regexp check constraint

Oracle 11.2.0.1
I need a customized using regexp expressions check constraint. We have a single column in our table REGNO, which is used to keep the registration number of our customers. It has alpha and numeric values, the first is Alpha and rest is digital with preceding zeros as A0100 A1245, C1111 etc. Sometimes, in the application user enters regnos evil if we want to stop entering the bad regnos i.e. assume that the user name is Ashok Kumar and in the series, we have 1000 users so this new user should have A1001 (other than any value A1001, in this example, the constraint must be limit to enter the value) only, not the others nor a1001 , A1000, nor A1002 or < has no > 1001 too. Rather than having 26 sequences (A to Z), we get a table where we have these columns:
Alpha char (1), number of LastNo. But sometimes a user enters wrong number value and stores it in the table, so next time for the same gap alpha arrives and confusing.
So, we must have a constraint of database level so that ONLY the correct values must be entered.
Kindly help me how I have this task please.
Thank you.

If REGNO is a derived value then why let you the user enter a value. Just generate the user.

Problem: by dropping a Table Check constraint

I got a check from a table constraint in my model. Then wanted to synchronize data dictionary. The comparison of models- dialogue see the difference, but as I check the box drop -(which is unchecked by default) and click the DOF preview preview is empty. I mean it's totally empty, not even the ddl-comments standard as
-Generated by Oracle SQL Developer Data Modeler 4.0.1.836
show up! So I guess that this behavior as a bug.
Dieter

Hi Dieter,

Thanks for reporting this problem. I connected a bug on this issue.

Note that this problem does not occur for check constraints that are defined in the definition of a column. It only occurs to verify the constraints defined at the Table level.

David

CHECK constraint

Hello experts,
I am new to oracle using sql developer in windows 7.i have a problem in which I must first make two tables:

Tbl_State (S_Id, S_Name, Country_Id)

and

tbl_City (C_Id, C_Name, State_Id)

.
I have to add a constraint to the tbl_city table so that it can accept only State_Id column values that are exist in the S_Id column in tbl_state. In that I tried to add a sub to mach check constraint query the values of tbl_state. S_Id but I think that Oracle sql does not query sub in the check constraint. Give me a suggestion how to fix this problem.
Thnak you
regrads
Aditya

Hello, Solomon,

I forgot to ask the OP to do first the column Tbl_state in the table as the primary key.

Regexp_like with check constraint
Hi all

My requirement is user does not enter data such as (½, ¼,...).
I created the table with the constraint validation with the following syntax:

CREATE TABLE mytest (c1 VARCHAR2 (20),)
CHECK (REGEXP_LIKE(c1,'^[[:alnum:]+[:digit:]+[!@#]]+$')));)

The means above, except alphanumeric, should enable figures and characters from the keyboard. But it does not have any character.

Please help me, any error in the syntax above.

Thank you
Mano
Alnum already includes numbers well, you don't need to Pack! @# in [] within []:
```
SQL> CREATE TABLE mytest (c1 VARCHAR2(20),
  2  CHECK (REGEXP_LIKE(c1,'^[[:alnum:]!@#]+$')));

Table created.

SQL> insert
  2    into mytest
  3    values('@xyz1abc')
  4  /

1 row created.

SQL> insert
  2    into mytest
  3    values('@xyz1abc*')
  4  /
insert
*
ERROR at line 1:
ORA-02290: check constraint (SCOTT.SYS_C0019122) violated

SQL>  
```
SY.

How to use current date in the check constraint
Hello
You could help me with this?
```
create table 
test_1 (
xxx number (1),
yyy number(1), 
zzz number(1), 
sss date check (sss < .......));
```
Thanks in advance for your help
Chanchal Wankhade wrote:
Hello
```
SQL> create table table_name (id number, tdate date check (jdate < sysdate));
create table table_name (id number, tdate date check (jdate < sysdate))
*
ERROR at line 1:
ORA-02438: Column check constraint cannot reference other columns
```
There are some workaround solutions...

And to add, that your mistake here is different - you're talking about another column JDATE (typo..?) in the check constraint... The actual column name is ADATE... :)

Published by: JAC on December 5, 2012 19:15

How to create Check Constraint that act as a foreign key?
Hi all

I have table EMP and Dept.

Can you give me "check constraint" sample for that when I get a (status = 'active') PGE unmatched entered DEPT., the process fails?
It will allow to enter the EMP with status = 'inactive' only even if no corresponding entry in the DEPT. Then foreign_key will not apply.

Thank you very much
Kins
I don't see why the performance should be a problem.

But the Council would always be to test your situation.

How to get the a table check constraint.
I don't see the function to get forced check.
I try the table.getCheckConstraints () function
but I return nothing.
Hello

table.getCheckConstraints () will return to check the constraints defined at the Table level in the Data Modeler.

You can also call column.getCheck (). This will return a check constraint defined on a column object in the Data Modeler.

David

Create the table using check constraints
I am trying to create a table with the following sql statement.

CREATE TABLE suppliers
(
supplier_id NULL NUMERIC (4).
supplier_name NULL VARCHAR2 (50).
Date1 DATE NULL,.
date2 DATE NULL CONSTRAINT CHECK check_date (date1 > date2)
);

I am gettign the following error

"ORA-02438: column check constraint cannot reference other columns.

How can I get this red using a trigger.
Help, please
Simply, you missed a comma after your last column and constraint.
```
ME_XE?CREATE TABLE suppliers
  2  (
  3  supplier_id NUMERIC(4) NULL ,
  4  supplier_name VARCHAR2(50) NULL ,
  5  date1 DATE NULL ,
  6  date2 DATE NULL ,
  7  CONSTRAINT check_date CHECK (date1 > date2)
  8  );

Table created.

Elapsed: 00:00:00.04
```

Date check constraint
Please can I get some help with a check constraint.

The Table is called the TITLE and the attribute is TI_RELDATE (a date). I am wanting to make sure that it is between 1930 and the date of the day.
Is this something like this:

CONSTRAINT TITLE_ck_TI_RELDATE CHECK (TI_RELDATE between 1930 and GETDATE())

Canning
GETDATE()-based you come from the side of SQL Server of the barrier. Literals in Oracle date are 'yyyy-mm-dd ". Now the part 'getdate '. What exactly are you trying to do? Make sure that the inserted/updated date to date is not a later date? If so, you need a trigger for this. Check constraint can do is make sure you inserted/updated date is 1930 or higher:
```
alter table tbl
  add constraint tbl_chk1
    check(
          dt >= date '1930-01-01'
         )
/
```
Switch to make sure that the inserted/updated date to date is not a later date:
```
create or replace
  trigger tbl_bir
    before insert
        or update
    of tbl
    for each row
    begin
        if dt > sysdate
          then
            raise_application_error(-20900,'Column dt value can't be a future date.');
        end if;
end;
/
```
SY.

Problem in creating the CHECK constraint

When creating a table, I want to apply a CHECK constraint, that pension_amount must be in accordance with pension_code, I get the below error.

CREATE TABLE pension_amount_check
(
   pension_amount         NUMBER (4),
   pension_code   NUMBER (1),
   CONSTRAINT amount_chk CHECK
      (CASE
          WHEN pension_code = 1 THEN (pension_amount = 3000 OR pension_amount > 3000)
          WHEN pension_code = 2 THEN pension_amount = 1500
       end)
)

ORA-00907: missing right parenthesis

How I can solve this problem.

Hello

So you cann which adds another.

CREATE TABLE PENSION_AMOUNT_CHECK
(
  PENSION_AMOUNT  NUMBER(4),
  PENSION_CODE    NUMBER(1)
)
/

ALTER TABLE PENSION_AMOUNT_CHECK ADD (
  CONSTRAINT SSSSSS
  CHECK (((pension_code =1) AND  (pension_amount = 3000 OR pension_amount > 3000)) OR (  (pension_code =1)  AND  pension_amount = 1500))  ENABLE NOVALIDATE)
/

* If the answer is correct, then mark it as a good answer

CHECK constraint question

Similar Questions

Maybe you are looking for