1 DEV 0 DEV DEV-997a1e22 73-75 The test should simulate the case when change set was applied to database, then someone have changed the file accidentally, committed the changes, and migration was triggered in prod. test/vcs4sql/sqlite/migration_test.rb @dgroup yurii.dubinka@gmail.com 2 DEV 0 DEV DEV-ca77ad7c 39-41 Raise the exception in case if - this.* are empty or null - conn is empty or null lib/vcs4sql/changelog.rb @dgroup yurii.dubinka@gmail.com 3 DEV 0 DEV DEV-b327c8c7 43-46 Wrap the sql's execution to separate blocks which will: - catch the error - provide the detailed description - populate the error code lib/vcs4sql/changelog.rb @dgroup yurii.dubinka@gmail.com 4 DEV 0 DEV DEV-20cb5df8 63-65 Lock the upgrade procedure in order to avoid the cases when multiple processes are going to modify/upgrade the same database schema. No concurrent upgrades is allowed so far. lib/vcs4sql/sqlite/migration.rb @dgroup yurii.dubinka@gmail.com 5 DEV 0 DEV DEV-4e0c8599 47-48 Add verification of array usage over index. The changelog shouldn't be a null. lib/vcs4sql/sqlite/applied.rb @dgroup yurii.dubinka@gmail.com 6 DEV 0 DEV DEV-41a82912 56-58 Add verification that connection not a null, throw error with proper error code in order to explain the problem. Potentially we need to define the class with error codes. lib/vcs4sql/sqlite/applied.rb @dgroup yurii.dubinka@gmail.com 7 DEV 0 DEV DEV-b96fff30 63-65 Raise an exception in case if any of arguments are null or empty. Potentially we may add verification of the type, but this is optional. lib/vcs4sql/sqlite/expected.rb @dgroup yurii.dubinka@gmail.com 9 DEV 0 DEV DEV-1214b7cd 1-2 Enable Travis CI as second CI server once the project became a public. This might be alternative for Circle CI (just in case) todo.yml @dgroup yurii.dubinka@gmail.com 10 DEV 0 DEV DEV-7f4f0ad5 4-5 Explain in readme.md how to use the project, add more instructions and generic guide. todo.yml @dgroup yurii.dubinka@gmail.com 11 DEV 0 DEV DEV-0cebd13d 7-8 There a lot of badges in readme which aren't enabled for now. Let's enable them. todo.yml @dgroup yurii.dubinka@gmail.com 12 DEV 0 DEV DEV-f11c7ae3 10-11 Publish a gem to the rubygems.org. Add this instructions to the @Rultor. No manual actions required. todo.yml @dgroup yurii.dubinka@gmail.com 13 DEV 0 DEV DEV-dab00982 13-14 Migrate to ruby 2.7.0. For now the project has 2.6.5. The project is new, it shouldn't be so expensive. todo.yml Yurii Dubinka yurii.dubinka@gmail.com 14 DEV 0 DEV DEV-7d90d09b 16-34 Think about support of Postgres, MySQL, Oracle and others. We need to reuse the existing structure as much as we can. Most of classes which are oriented on SQLite should be modified. The structure of potential upgrade folder might be the following ... |- lib |- test |- upgrade ||||- sqlite ||||||||- 00-define-initial-structure.sql ||||||||- 02-add-missing-foreign-keys.sql ||||||||- 03-add-missing-indexes.sql ||||||||- 99-add.testdata.sql ||||- postgres ||||||||- ... |||||- mysql ||||||||- ... |- Gemfile ... todo.yml Yurii Dubinka yurii.dubinka@gmail.com