All rules

Schema

postgresql/no-time-type

Disallow `TIME` / `TIMETZ` columns; they rarely model real values correctly.

  • Type suggestion
  • Recommended warn
  • Fixable no

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

Incorrect
CREATE TABLE shifts (id int, start_at time);
Incorrect
CREATE TABLE shifts (id int, start_at timetz);

Correct

Correct
CREATE TABLE shifts (id int, start_at timestamptz);
Correct
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

This rule has no options.

Try this rule

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.

0 errors 0 warnings parse 0ms · rules 0ms
Diagnostics

No issues found.

2 rules enabled.

Rule under test no-time-type — plus no-syntax-error as a safety net.
eslint-plugin-postgresql

An ESLint plugin that lints .sql files with real PostgreSQL grammar and a curated set of best-practice rules.

© 2026 eslint-plugin-postgresql contributors Built on libpg-query · PostgreSQL 17