It's only if I set id: false and expressly make the uuid column a primary key does it work: create_table :users, id: false do |t| If I try integrating mysql-binuuid-rails and add the column definition for uuid ( t.binary :uuid, limit: 16), I still get bad SQL: CREATE TABLE `users` (`id` uuid NOT NULL PRIMARY KEY, `uuid` varbinary(16), `name` varchar(255), `email` varchar(255), `created_at` datetime(6) NOT NULL, `updated_at` datetime(6) NOT NULL)

Which of course fails, since MySQL doesn't grok 'uuid' as a column type. If I follow the steps in the above tutorial, the SQL code Rails generates is: CREATE TABLE `users` (`id` uuid NOT NULL PRIMARY KEY, `name` varchar(255), `email` varchar(255), `created_at` datetime(6) NOT NULL, `updated_at` datetime(6) NOT NULL)įrom: class CreateUsers < ActiveRecord::Migration This tutorial uses PostgreSQL, and we're on MySQL (actually MariaDB), which doesn't have a 'uuid' column type. Is there a way for it to natively create / use a UUID column for primary keys, and to assume foreign keys are _UUID and char(36) rather than _id and int? G.orm :active_record, primary_key_type: :uuidīut it still doesn't seem like Rails is “natively” using UUIDs. timestamp_create), but to get Rails to include a primary key for UUID, we've had to build our migrations like this: class CreateLocations 'keyboard_uuid', :primary_key => 'uuid'įollowing some advice we found elsewhere, we have in config/initializers/generators.db: do |g| I just wanted a sanity check to make sure I'm not missing something? We followed the guidance here: (except we're using. The few times I've used RoR before (back in the 2.x/Rails 4 days), we just used the normal 'native' primary key functionality and relationships were as simple as belongs_to / has_one etc.įor this though we have to use UUIDs for primary keys, and while the Rails stuff can be made to work like that, it seems like a kludge. We're building an app in Ruby on Rails (Ruby 3, Rails 7.0.4, currently) with distributed MySQL (using replication).

Mariadb generate uuid