rails-migration

To use UUID primary keys in Rails migrations, enable the pgcrypto extension and define a uid column defaulting to gen_random_uuid(). This ensures your PostgreSQL tables generate secure, unique identifiers automatically.

Indexing UUID foreign keys in ActiveRecord requires explicitly naming indexes using the index_<table>_on_<column> convention. Avoid t.references for UUID tables and instead use *_uid suffixes for foreign key columns.

Yes, pgcrypto is required to generate UUID defaults in Rails on PostgreSQL. The extension provides the gen_random_uuid() function, which must be enabled before creating tables with UUID primary keys.

The best way to standardize Rails migration naming is to enforce explicit, consistent names like index_<table>_on_<column> for indexes and *_uid suffixes for foreign keys, ensuring predictable schema management.

Create tables in Rails migrations with bulk performance by using create_table bulk: true, defining a uid primary key with gen_random_uuid() default, and adding a unique index on the uid column.

Yes, PostgreSQL array columns can default to an empty array [], and boolean columns should have explicit defaults in Rails migrations. This prevents null values and ensures consistent data states.