One of my Rails migrations uses a uuid as the primary key. The Postgres extension gen_random_uuid()
should solve this issue, but I continue to get the error after installing the relevant extension (uuid-ossp
).
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试):
问题:
回答1:
The issue was that the uuid-ossp
extension was being blown away with the database each time I dropped the db as part of a reset and migration (e.g. rake db:drop db:create db:migrate
).
The fix is to create a migration that's run before all other migrations which enables the relevant extension(s). Like so (db/migrate/0_enable_extensions.rb
):
class EnableExtensions < ActiveRecord::Migration[5.1]
def change
enable_extension 'uuid-ossp'
enable_extension 'pgcrypto'
end
end
回答2:
Edge case answer:
Add the migration enabling the extension as stated above.
If you've previously had bigint
id's and you're converting over to UUID
, running rake db:reset db:migrate
failed for me. Be sure to run rake db:drop db:create db:migrate
as stated above!
If you get the error Environment data not found in the schema
, run bin/rails db:environment:set RAILS_ENV=development
.