Member Junction
    Preparing search index...
    • Type overlay, silence-respecting — the same rule decideBooleanOverlay applies to booleans.

      A source that states a type wins; a source that says NOTHING leaves the declaration alone. Without the silence check, MapSourceType('') fell through to its 'nvarchar' default and a describe with no type opinion quietly rewrote a curated datetimeoffset or bit to nvarchar — the exact "never fabricate values the source didn't give you" rule this file already enforces everywhere else. Types are hard constraints (real DDL), so a wrong one is a migration, not a cosmetic drift.

      A declaration that states nothing still takes the mapped value, fallback included: something has to be written, and there is no curated value to protect.

      Parameters

      • declaredType: string
      • sourceType: string

      Returns { value: string; winner: "Declared" | "Discovered" }