Recognises an expression running on one engine only
Check-constraint and default expressions pass through verbatim — the generator orders the column clauses per dialect (Oracle and Snowflake want DEFAULT before NOT NULL) but it cannot translate an expression. Look for vendor functions, regex operators, || versus +, and date arithmetic.
Can AI do this?
Not tested yet
No AI benchmark covers this knobit yet. New results are announced in the Can AI Do the Job? newsletter.
What it looks like in practice
Expected result: The vendor-specific expression and its portable form
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: ck_fact_payment_reference written as payment_reference ~ '^[A-Z0-9]{8,24}$'; it generates on all five targets and deploys only on Postgres. COALESCE(valid_to_date, 'infinity') in ck_dim_account_version_dates fails everywhere but Postgres Acceptable: Portable expressions only — comparisons, BETWEEN, IN, IS NULL, LENGTH: LENGTH(payment_reference) BETWEEN 8 AND 24 as the constraint and the pattern as a validity DQ rule; a closed end date instead of 'infinity'
Also known as: Expression that only runs on one engine (generated DDL)
Related knobits
Builds on
All 33 knobits of Generate and review DDL.
Source: Review checklist 08-ddl, row 9; ISO 9075; this skill (08-ddl.md)