All rules
Schema
postgresql/
Disallow `TIME` / `TIMETZ` columns; they rarely model real values correctly.
Why this matters
`time` has no date so cannot disambiguate around DST transitions; `timetz` stores an offset that is meaningless without a date. Use `timestamptz` for points in time, `interval` for durations, or `text` if all you need is a display value.
Examples
Incorrect
CREATE TABLE shifts (id int, start_at time);CREATE TABLE shifts (id int, start_at timetz);Correct
CREATE TABLE shifts (id int, start_at timestamptz);CREATE TABLE jobs (id int, duration interval);Configure it
// eslint.config.js
import postgresql from "eslint-plugin-postgresql";
export default [
{
files: ["**/*.sql"],
languageOptions: {
parser: postgresql.configs.recommended.languageOptions.parser,
},
plugins: { postgresql },
rules: {
"postgresql/no-time-type": "warn",
},
},
]; Options
Edit the SQL — only no-time-type is enabled.
Pre-filled with the first incorrect example. Toggle off in the rule shelf to see how the diagnostic disappears.
Diagnostics
No issues found.
2 rules enabled.
Rule under test
no-time-type — plus no-syntax-error as a safety net.