Enable strict SQL mode

Enable strict SQL mode | BeforeMerge Rules | BeforeMerge

Why this matters

Without strict mode, MySQL silently coerces invalid values: out-of-range numbers clamp, too-long strings truncate, and invalid dates become 0000-00-00. Strict mode turns these into errors so corruption is caught at write time.

-- Bad: lax mode silently truncates 'abc...300 chars' into a VARCHAR(255)
-- and clamps 99999 into a TINYINT.
 
-- Good: enforce strict mode
SET GLOBAL sql_mode =
  'STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION';

Why This Matters

Related Rules

Catch this automatically on every PR

Why this matters