Search before asking

• I searched the issues and found no similar issues.

Description

Consider the migration:

create or replace table important_table (
    insert_timestamp timestamp_ntz,
    name string,
);

What's wrong with this migration? Well you can't see it here but the table already exists, and the goal was just to add one new column, but the developer copied from the original migration and didn't consider that it's a destructive operation and will wipe the table. Instead an alter statement should have been used.

My team want to ensure that we catch issues which could lead to data-loss during development, and explicitely override/ignore with justification if needed.

We have tried using convention.blocked_words to achieve this, but neither blocked_words or blocked_regex have any support for whitespace, and so can't be used with "replace table" or "(replace\s table)"

Ideally there would be a way to warn about dangerous operations and ensure these are surfaced before or during code-review

Use case

No response

Dialect

snowflake

Are you willing to work on and submit a PR to address the issue?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct