Pick the smallest type that fits the domain instead of defaulting everything to text or bigint.
Oversized or stringly-typed columns waste storage, weaken validation, and slow indexes and scans.
BeforeMerge scans your pull requests against this rule and dozens more. Get actionable feedback before code ships.
Storing a timestamp as text or a boolean as a string defeats validation, bloats indexes, and blocks range queries. The narrowest correct type documents intent, lets the database validate values, and keeps storage and indexes compact.
-- Bad: everything is text or oversized
CREATE TABLE event (
created_at text, is_active text, priority bigint
);-- Good: types match the actual domain
CREATE TABLE event (
created_at timestamptz NOT NULL,
is_active boolean NOT NULL,
priority smallint NOT NULL
);