Change Primary Key Rails Migration

You can change the name of the primary key with the :primary_key option (don't forget to update the corresponding model) or, if you don't want a primary key at all, the main purpose of rails' migration feature is to issue commands that modify the schema using a consistent process. migrations can also be used to add or modify data.. Changing the name of primary key usually does very little besides adding a false sense of security - which is only by obscurity. you can however change the primary key from a auto-incrementing integer to a hash or some other sort of uuid. and there are many valid reasons to do so. this solely changes the method of generating primary keys.. Primarily, the schema file generated by rails will now omit the necessary sql instructions to actually make the custom primary key column a primary key in the database. our workaround. the first step to changing the primary key involves the migration file..

How to migrate high-load tables with zero downtime using

Adding a primary key id to table in rails just a quick little tip in case someone searches for it. i have a table that was used for a has_and_belongs_to_many (habtm) relationship – which was great earlier on.. I had a situation where i had to use different primary key column name over the default one(id) rails provide. as per the official guide:. by default, create_table will create a primary key called id.you can change the name of the primary key with the :primary_key option (don’t forget to update the corresponding model) or, if you don’t want a primary key at all, you can pass the option id. @vipulnsward you are right, i noticed that all migrations i created after upgrading to rails 5.1 have indeed a bigint as primary key. i just assumed that if i change < activerecord::migration[5.0] to < activerecord::migration[5.1] the older migrations would use that as well after resetting database and schema..

change primary key rails migration

visit link reference