Last updated 1 month ago
This ensures the accuracy and reliability of the data in the table. If there is any violation between the constraint and the data action, the action is aborted. ()
This syntax is partially supported.
<table-constraint> ::= [ CONSTRAINT <constraint-name> ] { { UNIQUE | PRIMARY KEY } ( <column-name> [ , … ] ) [ IN <dbspace-name> ] | <foreign-key-constraint> | CHECK ( <condition> ) } <foreign-key-constraint> ::= FOREIGN KEY [ <role-name> ] [ ( <column-name> [ , <column-name> ] … ) ] …REFERENCES <table-name> [ ( <column-name> [ , <column-name> ] … ) ] …[ <actions> ] [ IN <dbspace-name> ] <actions> ::= [ ON { UPDATE | DELETE } RESTRICT ]
CREATE TABLE t_constraint ( id1 INT NOT NULL, id2 INT PRIMARY KEY, age INT CHECK (age >= 18), email VARCHAR(255) UNIQUE, product_id INT REFERENCES products(id) ON DELETE RESTRICT IN SOMEPLACE, cod_iq VARCHAR(20) IQ UNIQUE(5), CONSTRAINT unq_name_email UNIQUE (name, email), CONSTRAINT fk_ord_line FOREIGN KEY (ord_id, line_id) REFERENCES ord_lines(ord_id,line_id) );
CREATE OR REPLACE TABLE t_constraint ( id1 INT NOT NULL, id2 INT PRIMARY KEY, age INT !!!RESOLVE EWI!!! /*** SSC-EWI-0035 - CHECK STATEMENT NOT SUPPORTED ***/!!! CHECK (age >= 18), email VARCHAR(255) UNIQUE, product_id INT REFERENCES products (id) ON DELETE RESTRICT , cod_iq VARCHAR(20) !!!RESOLVE EWI!!! /*** SSC-EWI-SY0003 - UNSUPPORTED IQ UNIQUE CONSTRAINT ***/!!! IQ UNIQUE(5), CONSTRAINT unq_name_email UNIQUE (name, email), CONSTRAINT fk_ord_line FOREIGN KEY (ord_id, line_id) REFERENCES ord_lines (ord_id, line_id) ) COMMENT = '{ "origin": "sf_sc", "name": "snowconvert", "version": { "major": 0, "minor": 0, "patch": "0" }, "attributes": { "component": "sybase", "convertedOn": "03/19/2025", "domain": "test" }}' ;
: CHECK STATEMENT NOT SUPPORTED.
: UNSUPPORTED IQ UNIQUE CONSTRAINT.