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
I found a note to this in an old issue, but it really ought to be in the readme because ...
by the time you push to heroku,
hit the error,
FIND the error,
then fix the error several commits back in your repo's to fix the migration (have to go back in history to fix it, can't add another migration later to fix it because the migration with :enum stops further migrations) is a real pain.
For that matter, is there any reason to recommend using :enum instead of :string in migrations in the first place?
The text was updated successfully, but these errors were encountered:
I found a note to this in an old issue, but it really ought to be in the readme because ...
by the time you push to heroku,
hit the error,
FIND the error,
then fix the error several commits back in your repo's to fix the migration (have to go back in history to fix it, can't add another migration later to fix it because the migration with :enum stops further migrations) is a real pain.
For that matter, is there any reason to recommend using :enum instead of :string in migrations in the first place?
The text was updated successfully, but these errors were encountered: