Skip to content

Conversation

@carlosdanielpohlod
Copy link

…ions

Checklist

  • [ x] I have read the Contribution & Best practices Guide.
  • [x ] My branch is up-to-date with the upstream master branch.
  • The tests pass locally with my changes.
  • I have added tests that prove my fix is effective or that my feature works(if appropriate).
  • I have added necessary documentation (if appropriate).

This merge request adds a version into ActiveRecord::Migration for old migrations to avoid the related exception.
Also, old rails methods used in migrations are replaced with your new versions.

Relationed issues:
#3099
#2665

Changes proposed in this pull request:

changes ActiveRecord::Migration to ActiveRecord::Migration[compatible version] in migration files;

changes use of update_attributes to update into migration;

changes get_all_versionsto the current version into the migration file

@carlosdanielpohlod carlosdanielpohlod force-pushed the backend/fix/migration/fix_versions branch from bf00ad7 to 9a253a6 Compare November 9, 2022 23:02
@carlosdanielpohlod
Copy link
Author

@hennevogel

@hennevogel hennevogel force-pushed the backend/fix/migration/fix_versions branch from 9a253a6 to 88bdfbf Compare April 19, 2023 11:38
@hennevogel hennevogel force-pushed the backend/fix/migration/fix_versions branch from 88bdfbf to 4eb451b Compare August 14, 2025 16:03
@hennevogel
Copy link
Member

Just do rails db:setup instead...

@hennevogel hennevogel closed this Aug 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants