DatabaseConsistency

The main goal of the project is to help you avoid various issues due to inconsistencies and inefficiencies between a database schema and application models.

If the project helps you or your organization, I would be very grateful if you contribute or donate.
Your support is an incredible motivation and the biggest reward for my hard work.

For detailed information, please read the wiki.

Currently, the tool can:

• find missing null constraints
• find missing length validations
• find missing presence validations
• find missing uniqueness validations
• find missing foreign keys for BelongsTo associations
• find missing unique indexes for uniqueness validation
• find missing indexes for HasOne and HasMany associations
• find primary keys with integer/serial type
• find mismatching primary key types with their foreign keys
• find redundant non-unique indexes
• find redundant uniqueness constraints
• find mismatching enum types with their values
• find mismatching foreign key cascades
• find inconsistent values between enums in the database and ActiveRecord’s enums/inclusion validations
• find redundant case_sensitive: false option for unique validations for case-insensitive types
• find missing null constraints on boolean fields
• find broken associations that refer undefined models
• find models that have missing tables
• find models with UUID primary keys without specified ordering column

Besides that, the tool provides:

• auto-correction
• flexible configuration
• slow start with TODO files
• support of customer checker

We support the following databases: SQLite3, PostgreSQL and MySQL.
We support ActiveRecord only at the moment. Please upvote the request for other frameworks if you’re interested.

Follow me and stay tuned for the updates:

• LinkedIn
• Medium
• Twitter
• GitHub

Usage

Add this line to your application’s Gemfile:

gem 'database_consistency', group: :development, require: false

And then execute:

$ bundle install

Example

$ bundle exec database_consistency
NullConstraintChecker fail User code column is required in the database but does not have a validator disallowing nil values
NullConstraintChecker fail User company_id column is required in the database but do not have presence validator for association (company)
LengthConstraintChecker fail Company note column has limit in the database but do not have length validator
MissingUniqueIndexChecker fail User name+email model should have proper unique index in the database
ForeignKeyChecker fail User company should have foreign key in the database
ForeignKeyTypeChecker fail User company associated model key (id) with type (integer) mismatches key (company_id) with type (integer(8))
MissingIndexChecker fail Company user associated model should have proper index in the database
ForeignKeyTypeChecker fail Company user associated model key (company_id) with type (integer(8)) mismatches key (id) with type (integer)
MissingIndexChecker fail Country users associated model should have proper index in the database
ColumnPresenceChecker fail User phone column should be required in the database
ColumnPresenceChecker fail User name column is required but there is possible null value insert
UniqueIndexChecker fail User index_users_on_name_and_slug index is unique in the database but do not have uniqueness validator
RedundantUniqueIndexChecker fail User index_users_on_name_and_slug index uniqueness is redundant as (index_users_on_slug) covers it
RedundantIndexChecker fail User index_users_on_phone index is redundant as (index_users_on_phone_and_slug) covers it
ColumnPresenceChecker fail User tmp column (tmp) is missing in table (users) but used for presence validation
ForeignKeyTypeChecker fail User something association (something) of class (User) relies on field (something_id) of table (users) but it is missing
ThreeStateBooleanChecker fail Company active boolean column should have NOT NULL constraint
MissingAssociationClassChecker fail Company anything refers to undefined model "Anything"
MissingTableChecker fail LegacyModel should have a table in the database
ImplicitOrderingChecker fail Secondary::User id implicit_order_column is recommended when using uuid column type for primary key

Funding

Open Collective Backers

You’re an individual who wants to support the project with a monthly donation. Your logo will be available on the Github page. [Become a backer]

Open Collective Sponsors

You’re an organization that wants to support the project with a monthly donation. Your logo will be available on the Github page. [Become a sponsor]

Contributing

Bug reports and pull requests are welcome on GitHub. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

Contributors

Code of Conduct

Everyone interacting in the DatabaseConsistency project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.

Changelog

DatabaseConsistency‘s changelog is available here.

Copyright

Copyright (c) Evgeniy Demin. See LICENSE.txt for further details.