Database governance built for humans and agents — controlling changes and access across every major database.
Go cicddata-governancedata-maskingdata-securitydatabase-accessdatabase-governancedevopsdevsecopsflywaygitopsliquibasemongodbmysqloraclepostgresqlschema-migrationssecuritysql-clientsqlservertidb
- statement: |-
CREATE TABLE CUSTOMER
(
ID INT PRIMARY KEY,
FULL_NAME VARCHAR(10),
POSITION VARCHAR(100)
);
changeType: 1
- statement: |-
CREATE TABLE CUSTOMER
(
ID INT,
FULL_NAME VARCHAR(10),
POSITION VARCHAR(100),
CONSTRAINT PK_CUSTOMER PRIMARY KEY (ID)
);
changeType: 1
- statement: |-
CREATE TABLE CUSTOMER
(
ID INT,
FULL_NAME VARCHAR(10),
POSITION VARCHAR(100)
);
changeType: 1
want:
- status: 2
code: 601
title: TABLE_REQUIRE_PK
content: Table CUSTOMER requires PRIMARY KEY.
startposition:
line: 1
column: 0
endposition: null
- statement: |-
CREATE TABLE CUSTOMER
(
ID INT PRIMARY KEY,
FULL_NAME VARCHAR(10),
POSITION VARCHAR(100)
);
ALTER TABLE CUSTOMER DROP PRIMARY KEY(ID);
changeType: 1
want:
- status: 2
code: 601
title: TABLE_REQUIRE_PK
content: Table CUSTOMER requires PRIMARY KEY.
startposition:
line: 7
column: 0
endposition: null
- statement: |-
CREATE TABLE CUSTOMER
(
ID INT,
FULL_NAME VARCHAR(10),
POSITION VARCHAR(100)
);
ALTER TABLE CUSTOMER ADD CONSTRAINT PK_CUSTOMER PRIMARY KEY (ID);
changeType: 1
- statement: |-
CREATE TABLE CUSTOMER
(
ID INT,
FULL_NAME VARCHAR(10),
POSITION VARCHAR(100)
);
ALTER TABLE "PUBLIC"."CUSTOMER" ADD CONSTRAINT PK_CUSTOMER PRIMARY KEY (ID);
changeType: 1
- statement: |-
CREATE TABLE CUSTOMER
(
ID INT,
FULL_NAME VARCHAR(10),
POSITION VARCHAR(100)
);
ALTER TABLE CUSTOMER ADD CONSTRAINT PK_CUSTOMER PRIMARY KEY (ID);
DROP TABLE CUSTOMER;
CREATE TABLE CUSTOMER
(
ID INT,
FULL_NAME VARCHAR(10),
POSITION VARCHAR(100)
);
changeType: 1
want:
- status: 2
code: 601
title: TABLE_REQUIRE_PK
content: Table CUSTOMER requires PRIMARY KEY.
startposition:
line: 9
column: 0
endposition: null
- statement: |-
CREATE TABLE CUSTOMER
(
ID INT,
FULL_NAME VARCHAR(10),
POSITION VARCHAR(100)
);
ALTER TABLE CUSTOMER ADD CONSTRAINT PK_CUSTOMER PRIMARY KEY (ID);
CREATE TABLE ORDERING
(
ORDER_ID INT PRIMARY KEY,
CUSTOMER_ID INT,
ORDER_DATE DATE,
TOTAL_AMOUNT DECIMAL(10, 2)
);
CREATE TABLE ADDRESS
(
ADDRESS_ID INT PRIMARY KEY,
STREET VARCHAR(100),
CITY VARCHAR(100),
STATE VARCHAR(100),
POSTAL_CODE VARCHAR(100),
COUNTRY VARCHAR(100)
);
ALTER TABLE CUSTOMER DROP PRIMARY KEY(ID);
ALTER TABLE ORDERING DROP PRIMARY KEY(ORDER_ID);
changeType: 1
want:
- status: 2
code: 601
title: TABLE_REQUIRE_PK
content: Table CUSTOMER requires PRIMARY KEY.
startposition:
line: 24
column: 0
endposition: null
- status: 2
code: 601
title: TABLE_REQUIRE_PK
content: Table ORDERING requires PRIMARY KEY.
startposition:
line: 25
column: 0
endposition: null
# Test case to verify correct line positions for multi-statement scenarios.
# Each table should report the line where its PRIMARY KEY was dropped,
# not the line of the last statement.
- statement: |-
CREATE TABLE t1 (id INT PRIMARY KEY);
ALTER TABLE t1 DROP PRIMARY KEY(id);
CREATE TABLE t2 (id INT PRIMARY KEY);
ALTER TABLE t2 DROP PRIMARY KEY(id);
changeType: 1
want:
- status: 2
code: 601
title: TABLE_REQUIRE_PK
content: Table t1 requires PRIMARY KEY.
startposition:
line: 2
column: 0
endposition: null
- status: 2
code: 601
title: TABLE_REQUIRE_PK
content: Table t2 requires PRIMARY KEY.
startposition:
line: 4
column: 0
endposition: null