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
{{ message }}
This repository has been archived by the owner on Jul 24, 2020. It is now read-only.
Due to the fact that we deployed an earlier version to DEV before reverting the ordering changes (in #1697), our DEV instances currently have an extra ordering column in the equipment_models table in their db schema that isn't reflected in Rails and prevents new Equipment Models from being created. In order to fix this we should refresh all DEV databases from the current PROD instances and re-run migrations (since the offending migration has since been removed). We should also update our CHANGELOG for v6.3.0 to remove the line about equipment model ordering.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Due to the fact that we deployed an earlier version to DEV before reverting the ordering changes (in #1697), our DEV instances currently have an extra ordering column in the equipment_models table in their db schema that isn't reflected in Rails and prevents new Equipment Models from being created. In order to fix this we should refresh all DEV databases from the current PROD instances and re-run migrations (since the offending migration has since been removed). We should also update our CHANGELOG for v6.3.0 to remove the line about equipment model ordering.
The text was updated successfully, but these errors were encountered: