fix-db-schema-conflicts

It prevents db/schema.rb conflicts in your Rails projects when working with multiple team members.

Specifically the situation that goes like this:

John is working on a feature, and adds a migration to create an updated_at timestamp to Task. Sara is working on a different feature, and adds a migration to create a name column to Task. They both run their migrations locally, and then get a new copy of master with the other's feature and migration. Then when they run migrations again, John's tasks table looks like this:

t.timestamp :updated_at
t.string :name

And Sara's looks like this:

t.string :name
t.timestamp :updated_at

And every time they run migrations before committing new code, their db/schema.rb file will be showing a change, because they are flipping the order of the columns.

By using the fix-db-schema-conflicts gem, this problem goes away.

How it works

This gem sorts the table, index, extension, and foreign key names before outputting them to the schema.rb file. Additionally it runs Rubocop with the auto-correct flag to ensure a consistent output format.

Usage

You don't have to do anything different. It should just work. Simply run rake db:migrate or rake db:schema:dump as you would before and fix-db-schema-conflicts will do the rest.

Installation

Add this line to your application's Gemfile in your development group:

gem 'fix-db-schema-conflicts'

And then execute:

$ bundle

Older versions of Rubocop:

This gem works with versions of Rubocop >= 0.52.0. Use version 3.0.3 if you wish to use an earlier version of Rubocop.

Older versions of Ruby:

This gem works with Ruby >= 2.4. Use version 3.0.3 if you wish to use an earlier version of Ruby.

Contributing

1. Fork it (https://github.com/[my-github-username]/fix-db-schema-conflicts/fork)
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

Contributors

• @jakeonrails - Creator and maintainer
• @TCampaigne
• @Lordnibbler
• @timdiggins
• @zoras
• @jensljungblad
• @vsubramanian
• @claytron
• @amckinnell
• @rosscooperman

Releases

• 4.1.0
  • Added support for new Rubocop 0.79+ schema (amckinnell)
  • Bump development dependencies (amckinnell)
• 4.0.0
  • Improve performance
  • Better compatibility with Rails db:schema:dump task
  • Only support Ruby 2.4+
  • Only support Rails 5.x
  • Only support Rubocop 0.52+
  • Bump development dependencies
• 3.0.3
  • Added support for new Rubocop 0.53+ schema (rosscooperman)
• 3.0.2
  • Added support for new Rubocop 0.49+ schema (amckinnell)
• 3.0.1
  • Improve formatting to be more consistent (amckinnell)
  • Bump rake dependency to bypass a rake bug in older version (amckinnell)
• 3.0.0
  • Only support Ruby 2.2+ since lower versions have reached EOL.
• 2.0.1
  • Fix bug that caused failure when project directory has a space in it
• 2.0.0
  • Allow usage of Rubocop >= 0.38.0
  • Remove Rails 5 deprecation warnings for using alias_method_chain
  • This upgrade breaks compatibility with Ruby 1.9x since 1.9x lacks #prepend
• 1.2.2
  • Remove dependency on sed
• 1.2.1
  • Upgrade Rubocop to get major performance boost
  • Add support for sorting of extensions
  • Fix spacing regression introduced by Rubocop upgrade
  • Add test suite and an integration test