Skip to content

Database governance built for humans and agents — controlling changes and access across every major database.

2.2 KB
Raw Blame
- statement: DROP DATABASE DB;
  changeType: 1
  want:
    - status: 2
      code: 101
      title: SCHEMA_BACKWARD_COMPATIBILITY
      content: Drop database "DB" may cause incompatibility with the existing data and code
      startposition:
        line: 1
        column: 0
      endposition: null
- statement: DROP SCHEMA SCHEMA1;
  changeType: 1
  want:
    - status: 2
      code: 112
      title: SCHEMA_BACKWARD_COMPATIBILITY
      content: Drop schema "TEST_DB.SCHEMA1" may cause incompatibility with the existing data and code
      startposition:
        line: 1
        column: 0
      endposition: null
- statement: DROP TABLE T;
  changeType: 1
  want:
    - status: 2
      code: 103
      title: SCHEMA_BACKWARD_COMPATIBILITY
      content: Drop table "TEST_DB.PUBLIC.T" may cause incompatibility with the existing data and code
      startposition:
        line: 1
        column: 0
      endposition: null
- statement: ALTER TABLE T DROP COLUMN COL1;
  changeType: 1
  want:
    - status: 2
      code: 105
      title: SCHEMA_BACKWARD_COMPATIBILITY
      content: Drop column "COL1" may cause incompatibility with the existing data and code
      startposition:
        line: 1
        column: 0
      endposition: null
- statement: |-
    CREATE TABLE IF NOT EXISTS T(ID INT);
    DROP TABLE T;
  changeType: 1
  want:
    - status: 2
      code: 103
      title: SCHEMA_BACKWARD_COMPATIBILITY
      content: Drop table "TEST_DB.PUBLIC.T" may cause incompatibility with the existing data and code
      startposition:
        line: 2
        column: 0
      endposition: null
- statement: |-
    CREATE TABLE T(ID INT);
    DROP TABLE T;
  changeType: 1
# DIVERGENCE LOCK (omni migration): legacy fired CompatibilityDropTable here only
# because its ANTLR listener never subscribed to the Create_table_like context —
# an accidental gap, not intent. omni folds CREATE TABLE ... LIKE into
# CreateTableStmt, so a LIKE-created table dropped in the SAME batch is treated
# like any other in-batch creation (no advice), matching the rule's intent and
# the behavior both versions already had for plain CREATE + DROP.
- statement: CREATE TABLE SCRATCH LIKE SOURCE_TABLE;DROP TABLE SCRATCH;
  changeType: 1
  want: null