casa
casa copied to clipboard
Fix problem where running migrations changes db ids from integer to bigint and back
Fix problem where running migrations changes db ids from integer to bigint and back
They should be bigint
The problem seems to be the difference between rake db:drop db:create db:migrate
and rake db:setup
Hi! Is this still happening? I couldn't reproduce the error.
Hi, yes it's still happening. For me, for example, when I run rake db:migrate
some ids change from bigint to integer
The problem seems to be the difference between rake db:drop db:create db:migrate and rake db:setup :/
This is a known bug that has been addressed in Rails: https://github.com/rails/rails/issues/45093 If you're having this issue locally, you have to drop your database locally and recreate it!