> For the complete documentation index, see [llms.txt](https://ploegert.gitbook.io/til/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ploegert.gitbook.io/til/programmy/rails/add-timestamptz-columns-with-the-migration-dsl.md).

# Add timestamptz Columns With The Migration DSL

The Rails migration DSL comes with the [`t.timestamps`](https://edgeapi.rubyonrails.org/classes/ActiveRecord/ConnectionAdapters/TableDefinition.html#method-i-timestamps) method. This allows you to add the `created_at` and `updated_at` timestamp columns that are standard for most models in Rails apps.

```ruby
create_table :posts do |t|
  t.string :title, null: false
  # ...

  t.timestamps
end
```

With a PostgreSQL database, this will result in a `posts` table that has `created_at` and `updated_at` columns that are of type `timestamp(6) without time zone`.

I'd prefer to use timestamp columns that include a time zone offset. PostgreSQL supports this with its [`timestamptz` (`timestamp with time zone`)](https://www.postgresql.org/docs/current/datatype-datetime.html) data type.

We can tell the Rails DSL to generate this type of column by abondoning the `t.timestamps` method and instead creating custom columns with [`t.column`](https://edgeapi.rubyonrails.org/classes/ActiveRecord/ConnectionAdapters/TableDefinition.html#method-i-column).

```ruby
create_table :posts do |t|
  t.string :title, null: false
  # ...

  t.column :created_at, :timestamptz, null: false
  t.column :updated_at, :timestamptz, null: false
end
```

It is a little less convenient than the `t.timestamps` helper, but it is nice to know we can have a little more control over the data type.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ploegert.gitbook.io/til/programmy/rails/add-timestamptz-columns-with-the-migration-dsl.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.