Always have id, created_at, updated_at columns in PostgreSQL
All CREATE TABLE statements must include `id`, `created_at`, and `updated_at` columns.
Bad:
```sql
CREATE TABLE users (
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL
);
Install this rule for wispbit
Add this rule to wispbit and it will run when you open a pull request
Install this rule for Coderabbit
Copy the configuration below and add it to your repository as .coderabbit.yml
in your project root.
reviews:
path_instructions:
- path: "*.sql"
instructions: |
All CREATE TABLE statements must include `id`, `created_at`, and `updated_at` columns.
Bad:
```sql
CREATE TABLE users (
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL
);
```
Good:
```sql
CREATE TABLE users (
id SERIAL PRIMARY KEY,
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL,
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL,
updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL
);
```
Install this rule for Greptile
Greptile rules can be added through the web interface. Please see this documentation for details on how to add custom rules and context.
All CREATE TABLE statements must include `id`, `created_at`, and `updated_at` columns.
Bad:
```sql
CREATE TABLE users (
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL
);
```
Good:
```sql
CREATE TABLE users (
id SERIAL PRIMARY KEY,
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL,
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL,
updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL
);
```
File Path Patterns:
Install this rule for GitHub Copilot
Copilot instructions can be added through the interface. See the documentation for details on how to create coding guidelines.
All CREATE TABLE statements must include `id`, `created_at`, and `updated_at` columns.
Bad:
```sql
CREATE TABLE users (
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL
);
```
Good:
```sql
CREATE TABLE users (
id SERIAL PRIMARY KEY,
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL,
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL,
updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL
);
```
File Path Patterns:
Install this rule for Graphite Diamond
Diamond custom rules can be added through the interface. See the documentation for details on how to create custom rules.
All CREATE TABLE statements must include `id`, `created_at`, and `updated_at` columns.
Bad:
```sql
CREATE TABLE users (
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL
);
```
Good:
```sql
CREATE TABLE users (
id SERIAL PRIMARY KEY,
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL,
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL,
updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL
);
```
File Path Patterns:
Use with Cline
Copy the rule below and ask Cline to review your code using this rule
All CREATE TABLE statements must include `id`, `created_at`, and `updated_at` columns.
Bad:
```sql
CREATE TABLE users (
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL
);
```
Good:
```sql
CREATE TABLE users (
id SERIAL PRIMARY KEY,
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL,
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL,
updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL
);
```
Use with OpenAI Codex
Copy the rule below and ask OpenAI Codex to review your code using this rule
All CREATE TABLE statements must include `id`, `created_at`, and `updated_at` columns.
Bad:
```sql
CREATE TABLE users (
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL
);
```
Good:
```sql
CREATE TABLE users (
id SERIAL PRIMARY KEY,
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL,
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL,
updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL
);
```
Use with Cursor
Copy the rule below and ask Cursor to review your code using this rule
All CREATE TABLE statements must include `id`, `created_at`, and `updated_at` columns.
Bad:
```sql
CREATE TABLE users (
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL
);
```
Good:
```sql
CREATE TABLE users (
id SERIAL PRIMARY KEY,
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL,
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL,
updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL
);
```
Use with Claude Code
Copy the rule below and ask Claude Code to review your code using this rule
All CREATE TABLE statements must include `id`, `created_at`, and `updated_at` columns.
Bad:
```sql
CREATE TABLE users (
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL
);
```
Good:
```sql
CREATE TABLE users (
id SERIAL PRIMARY KEY,
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL,
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL,
updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL
);
```
Install this rule for Windsurf
To set up rules for Windsurf Reviews, please see this documentation
All CREATE TABLE statements must include `id`, `created_at`, and `updated_at` columns.
Bad:
```sql
CREATE TABLE users (
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL
);
```
Good:
```sql
CREATE TABLE users (
id SERIAL PRIMARY KEY,
email VARCHAR(255) NOT NULL UNIQUE,
name VARCHAR(100) NOT NULL,
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL,
updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL
);
```