You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our team is using this gem successfully, the schema.db is pretty well sorted. But when I run migrations or rollbacks on my local machine (on MacOS), the schema is getting unsorted, having exactly the order as it is in the DB. Is it my Mac guilty?
Also, a little nitpick - the 'rails', '~> 4.2.0' is specified in the gemspec, and the tests are running OK. But when changing to 'rails', '~> 5.2.0', the integration_spec fails, because on migration add_index is put into the schema inside the table as t.index.
The text was updated successfully, but these errors were encountered:
Our team is using this gem successfully, the schema.db is pretty well sorted. But when I run migrations or rollbacks on my local machine (on MacOS), the schema is getting unsorted, having exactly the order as it is in the DB. Is it my Mac guilty?
Also, a little nitpick - the
'rails', '~> 4.2.0'
is specified in the gemspec, and the tests are running OK. But when changing to'rails', '~> 5.2.0'
, the integration_spec fails, because on migrationadd_index
is put into the schema inside the table ast.index
.The text was updated successfully, but these errors were encountered: