Fix `bin/rails db:migrate` with specified `VERSION` #30714

bogdanvlviv · 2017-09-25T21:16:06Z

Fix bin/rails db:migrate with specified VERSION.
bin/rails db:migrate with empty VERSION behaves as without VERSION.
Check a format of VERSION: Allow a migration version number
or name of a migration file. Raise error if format of VERSION is invalid.
Raise error if target migration doesn't exist.

Related to #30707

/cc @matthewd

rails-bot · 2017-09-25T21:16:21Z

r? @eileencodes

(@rails-bot has picked a reviewer for you, use r? to override)

eileencodes · 2017-09-29T12:13:28Z

activerecord/lib/active_record/migration.rb

-        result = execute_migration_in_transaction(migration, @direction)
+        if invalid_target?
+          raise UnknownMigrationVersionError.new(@target_version)
+        end


What does the error message say for the UnknownMigrationVersionError? I'm wondering if it's user friendly enough like "0.1.1" is an unknown migration number please run with VERSION=123. I'm concerned about inexperienced users not realizing their VERSION env var is set elsewhere and how to set it for the Rails migrations.

eileencodes · 2017-09-29T12:16:30Z

I think this is fine as a bandaid fix, but I'm not sure whether this is a good long term solution. Think about this usecase:

VERSION is set in an env var
User goes to run migration and doesn't realize that VERSION is set
They can't run rake db:migrate with VERSION manually because they don't want a version, they want to run a bunch of migrations at once
What do they do now? Unset VERSION to run the migrations and then reset it?

I worry that this PR instead will completely block migrations without a clear path forward causing a lot of friction in the migration process.

bogdanvlviv · 2017-10-05T19:15:01Z

Thanks, @eileencodes. This PR doesn't fix the issue #30707 (but related to this issue), it just fix our current implementation that we have.

Currently, if run rails db:migrate and set VERSION as a negative number, it'll revert all migrations. It is a bug and this PR just fixes it.

Example:
Before:

$ rails db:migrate:status

 Status   Migration ID    Migration Name
--------------------------------------------------
   up     20171005143525  One
   up     20171005143538  Two
   up     20171005143556  Three

$ rails db:migrate VERSION=1
rails aborted!
ActiveRecord::UnknownMigrationVersionError:

No migration with version number 1.

# There is bug
$ rails db:migrate VERSION=-1
ubuntu@ubuntu-xenial:/active_projects/zz$ rails db:migrate VERSION=-1
== 20171005143556 Three: reverting ============================================
== 20171005143556 Three: reverted (0.4047s) ===================================

== 20171005143538 Two: reverting ==============================================
== 20171005143538 Two: reverted (0.0000s) =====================================

== 20171005143525 One: reverting ==============================================
== 20171005143525 One: reverted (0.0000s) =====================================

After:

$ rails db:migrate:status

 Status   Migration ID    Migration Name
--------------------------------------------------
   up     20171005143525  One
   up     20171005143538  Two
   up     20171005143556  Three

$ rails db:migrate VERSION=1
rails aborted!
ActiveRecord::UnknownMigrationVersionError:

No migration with version number 1.

# Fixed
$ rails db:migrate VERSION=-1
rails aborted!

About the case:

VERSION is set in an env var

User goes to run migration and doesn't realize that VERSION is set

They can't run rake db:migrate with VERSION manually because they don't want a version, they want
to run a bunch of migrations at once
What do they do now? Unset VERSION to run the migrations and then reset it?

I think the main reason of the problem in common name of environment variable that we use VERSION. It is a too common name and not only Rails can pretend for this variable. So I would recommend to deprecate using of VERSION in favor of new RAILS_MIGRATION_VERSION for Rails 5.2 and remove for Rails 6.0. Also, it'll look more consistent with other environment variables like RAILS_CACHE_ID, RAILS_MASTER_KEY, RAILS_ENV.

What do you think about deprecation of using VERSION in favor of RAILS_MIGRATION_VERSION?
Would love to hear your thought about it or any better solutions if exist. If my solution is good, I'll happy to open PR that will do it.
Thanks!

matthewd · 2017-10-05T23:40:12Z

Can we validate the supplied version before we call to_i, so that 0.1.2 will fail? (For better compatibility with what people might be doing, we should probably ignore anything following an underscore, though: AIUI, passing a full migration filename will currently work, so let's not break that.)

Renaming the variable is not appropriate: unlike the others you mentioned, it's intended to be set on the rake command line; the others are intended to suitable for setting more globally across a session. (And I believe that's the stronger convention in general: the more broadly a variable is visible, the more specifically it should be named.) Naming such a redundant variable on a db:migrate command would be difficult (more prone to typos), and ugly.

It would also be an unnecessary stopgap: the ability to pass proper arguments to commands, instead of using ugly env vars, is a large motivation for our ongoing effort to convert rake-based commands to thor. Once we've done db:migrate, this can use --target-version 123 or something instead.

We've been using VERSION for 10 years: it doesn't seem worth the disruption to make everyone adjust their invocations when we know it'll change again soon, for a complaint I don't recall ever having seen before. Stricter input validation is a proportional response... and we can focus any remaining energy on the Command-ification effort.

matthewd · 2017-10-05T23:47:03Z

If someone does have VERSION set in an env var, they would currently have the problem described in #30707 -- they'd never be able to migrate properly, because we'd always be aiming for whatever version we thought it was asking for. So a change from "valiantly attempting to do something they didn't intend" into "refusing to act" won't affect anyone, I don't think: either they've already worked around the variable being set, or such people don't exist.

I haven't checked, but I assume they can run the command with rails db:migrate VERSION= (i.e., blank), and that should be treated the same as if the variable wasn't set at all. That will continue to work with any change we make here. (And if it doesn't currently, let's make it.)

bogdanvlviv · 2017-10-06T09:46:54Z

@matthewd I think I got your point. I just added the changes that check VERSION.
It prevents reverting all migrations if VERSION looks like "negative number", 0.1.11, unknown etc.
If user needs revert all migrations, he should set VERSION to 0 as it is documented.
(Not the changes fix case from #30707)

This PR shouldn't break our current implementation that we have and AIUI we can apply new strict behavior(See #30714 (comment)).

Could you please review and provide feedback about behavior that this PR provides?

If this behavior doesn't fit, I'll try to find another implementation 😄 but I guess we are moving in the right direction.

Thank you for the response! ❤️

matthewd · 2017-10-06T09:55:14Z

activerecord/lib/active_record/tasks/database_tasks.rb

          scope.blank? || scope == migration.scope
        end
        ActiveRecord::Base.clear_cache!
      ensure
        Migration.verbose = verbose_was
      end

+      def check_target_version
+        if ENV["VERSION"] && ENV["VERSION"].empty?
+          raise "Empty VERSION provided"


As I mentioned, I think an empty VERSION should be treated just the same as when it's not set at all, so people can easily override a more widely-set variable. Before we kill it though, can you see any history on why we added the existing emptiness check?

Checking for empties of VERSION is added by #28485 because db:migrate:redo, db:migrate:up, db:migrate:down require VERSION,
but db:migrate doesn't require VERSION, so I think it db:migrate with empty VERSION should behave as without VERSION.

matthewd · 2017-10-06T09:56:27Z

activerecord/lib/active_record/tasks/database_tasks.rb

+          raise "Empty VERSION provided"
+        end
+
+        if target_version == 0 && ENV["VERSION"].strip.length != 1


This sounds like an overly-special case. 1.2.3 should raise too, even if there's a migration number 1.

matthewd · 2017-10-06T10:00:51Z

activerecord/lib/active_record/tasks/database_tasks.rb

+
+        if target_version == 0 && ENV["VERSION"].strip.length != 1
+          raise(
+            "Invalid format of target version: \n\n        `VERSION=#{ENV['VERSION']}`"


I don't think we need the fancy spacing here

matthewd · 2017-10-06T10:03:04Z

railties/test/application/rake/migrations_test.rb

@@ -206,6 +278,46 @@ class AMigration < ActiveRecord::Migration::Current
        end
      end

+      test "raise error on any move when target migration does not exist" do
+        app_file "db/migrate/01_one_migration.rb", <<-MIGRATION


I'd like to see a test somewhere (assuming we don't already have one, though I haven't checked) to ensure that VERSION=01_one_migration.rb will work, even after we make VERSION=1.2 fail.

I'd like to see a test somewhere (assuming we don't already have one, though I haven't checked) to ensure that VERSION=01_one_migration.rb will work, even after we make VERSION=1.2 fail.

I just implemented this behavior and added test cases.

bogdanvlviv · 2017-10-16T11:20:31Z

@matthewd What do you think about current behavior that is implemented by this PR?

bogdanvlviv · 2017-10-19T16:54:32Z

activerecord/lib/active_record/tasks/database_tasks.rb

          scope.blank? || scope == migration.scope
        end
        ActiveRecord::Base.clear_cache!
      ensure
        Migration.verbose = verbose_was
      end

+      def check_target_version
+        if target_version && !(Migration::MigrationFilenameRegexp.match?(ENV["VERSION"]) || /\A\d+\z/.match?(ENV["VERSION"]))


@matthewd What do you think about this condition?

bogdanvlviv · 2017-10-30T22:09:06Z

let me know if there is something i should to do.

bogdanvlviv · 2017-11-06T22:14:21Z

Could you please provide any feedback about this PR?

rafaelfranca · 2017-11-06T22:34:30Z

activerecord/lib/active_record/tasks/database_tasks.rb

+      end
+
+      def target_version
+        return ENV["VERSION"].to_i if ENV["VERSION"] && !ENV["VERSION"].empty?


✂️ the return

Ensure that `bin/rails db:migrate` with specified `VERSION` reverts all migrations only if `VERSION` is `0`. Raise error if target migration doesn't exist.

rails-bot assigned eileencodes Sep 25, 2017

eileencodes mentioned this pull request Sep 27, 2017

VERSION in environment value used for rake db:migrate causing catastrophic issues #30707

Closed

eileencodes reviewed Sep 29, 2017

View reviewed changes

bogdanvlviv force-pushed the fix-rails_db_migrate_VERSION branch from 26ff22f to 36db0ee Compare October 5, 2017 19:09

bogdanvlviv force-pushed the fix-rails_db_migrate_VERSION branch 2 times, most recently from 849b6cc to 8ab4dd8 Compare October 5, 2017 19:44

bogdanvlviv force-pushed the fix-rails_db_migrate_VERSION branch 2 times, most recently from dd8c82a to e3563da Compare October 6, 2017 09:42

matthewd reviewed Oct 6, 2017

View reviewed changes

bogdanvlviv force-pushed the fix-rails_db_migrate_VERSION branch 3 times, most recently from d66e70a to 8b2f5e2 Compare October 9, 2017 21:39

bogdanvlviv force-pushed the fix-rails_db_migrate_VERSION branch 2 times, most recently from 352278a to 7822c6b Compare October 19, 2017 15:14

bogdanvlviv commented Oct 19, 2017

View reviewed changes

bogdanvlviv force-pushed the fix-rails_db_migrate_VERSION branch 3 times, most recently from ce8398c to 5b8b225 Compare October 30, 2017 20:15

rafaelfranca requested changes Nov 6, 2017

View reviewed changes

Fix bin/rails db:migrate with specified VERSION

90fe2a4

Ensure that `bin/rails db:migrate` with specified `VERSION` reverts all migrations only if `VERSION` is `0`. Raise error if target migration doesn't exist.

bogdanvlviv force-pushed the fix-rails_db_migrate_VERSION branch from 5b8b225 to 90fe2a4 Compare November 6, 2017 22:44

rafaelfranca merged commit 212481b into rails:master Nov 7, 2017

bogdanvlviv deleted the fix-rails_db_migrate_VERSION branch November 7, 2017 05:50

jarthod mentioned this pull request Sep 23, 2021

Running rake db:migrate when version is the newest rollsback the migration. adacosta/mongoid_rails_migrations#30

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix `bin/rails db:migrate` with specified `VERSION` #30714

Fix `bin/rails db:migrate` with specified `VERSION` #30714

bogdanvlviv commented Sep 25, 2017 •

edited

rails-bot commented Sep 25, 2017

eileencodes Sep 29, 2017 •

edited

eileencodes commented Sep 29, 2017

bogdanvlviv commented Oct 5, 2017 •

edited

matthewd commented Oct 5, 2017

matthewd commented Oct 5, 2017

bogdanvlviv commented Oct 6, 2017

matthewd Oct 6, 2017

bogdanvlviv Oct 8, 2017

matthewd Oct 6, 2017

matthewd Oct 6, 2017

matthewd Oct 6, 2017

bogdanvlviv Oct 8, 2017

bogdanvlviv commented Oct 16, 2017

bogdanvlviv Oct 19, 2017

bogdanvlviv commented Oct 30, 2017

bogdanvlviv commented Nov 6, 2017

rafaelfranca Nov 6, 2017

bogdanvlviv Nov 6, 2017

Fix bin/rails db:migrate with specified VERSION #30714

Fix bin/rails db:migrate with specified VERSION #30714

Conversation

bogdanvlviv commented Sep 25, 2017 • edited

rails-bot commented Sep 25, 2017

eileencodes Sep 29, 2017 • edited

Choose a reason for hiding this comment

eileencodes commented Sep 29, 2017

bogdanvlviv commented Oct 5, 2017 • edited

matthewd commented Oct 5, 2017

matthewd commented Oct 5, 2017

bogdanvlviv commented Oct 6, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bogdanvlviv commented Oct 16, 2017

Choose a reason for hiding this comment

bogdanvlviv commented Oct 30, 2017

bogdanvlviv commented Nov 6, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Fix `bin/rails db:migrate` with specified `VERSION` #30714

Fix `bin/rails db:migrate` with specified `VERSION` #30714

bogdanvlviv commented Sep 25, 2017 •

edited

eileencodes Sep 29, 2017 •

edited

bogdanvlviv commented Oct 5, 2017 •

edited