Recognises a type meaning something else on another engine
One modelled type rendering to a different meaning per engine. TIMESTAMP is a row-version counter in T-SQL (emitted DATETIME2(6)) and 32-bit, 2038-bounded and session-time-zone-converting in MySQL (emitted DATETIME); BOOLEAN becomes NUMBER(1) on Oracle and TINYINT(1), which accepts 42, on MySQL; Databricks collapses VARCHAR(n) to STRING.
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 type and its meaning on each engine
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: is_business_day BOOLEAN on MySQL becomes TINYINT(1) with no check and a loader writes 2 for a half day. account_number VARCHAR(20) on Databricks accepts a 34-character value, and the joins to fact_payment start missing Acceptable: A check constraint for the 0/1 domain wherever the engine has no boolean, and the modelled length kept as a DQ rule on every target that does not enforce it — the header note says which ones those are
Also known as: Type that silently means something else (generated DDL)
Related knobits
Builds on
All 33 knobits of Generate and review DDL.
Source: Review checklist 08-ddl, row 12; ISO 9075; this skill (08-ddl.md)