One of the things that has really bugged me with recent Typo development is the pain of maintaining 3 different database schema files (PostgreSQL, MySQL, SQLite) along with a set of Rails DB migration scripts. Every time we add a new table, we have to edit 4 different files, even though all of the information that we need is available in the migration file. Unfortunately, without the static schemas, new users would be adrift, so we’re stuck having to hand-modify each of the static schema files. This violates the DRY principle, causes errors, and irritates developers.
So I figured I’d fix it by writing some code that can take a set of Rails DB migrations, fold, spindle, and mutilate Rails itself, and then spit out a database-specific schema file showing all of the tables, indexes, and seed data provided by the migration files. This includes handling cases where a table is added in migration #4, two new fields are added in migration #6, and one field is deleted in migration #9. There are some corner cases that just can’t be handled, mostly relating to seed data that needs to be migrated to be correct with more recent schemas, but I think I can come close enough to make Typo happy, and probably a lot of other open-source Rails projects.
This turned out to be easier then I expected. I’ve put about 4 hours into it so far, and I can take this migration:
# This is db/migrate/4_test4.rb class Test4 < ActiveRecord::Migration def self.up create_table :sidebars do |t| t.column :controller, :string t.column :active_position, :integer t.column :active_config, :text t.column :staged_position, :integer t.column :staged_config, :text end Sidebar.create(:active_position=>0, :controller=>'category') Sidebar.create(:active_position=>1, :controller=>'static') Sidebar.create(:active_position=>2, :controller=>'xml') end def self.down drop_table :sidebars end end
And then do this:
$ irb irb(main):001:0> require 'migrate' => true irb(main):002:0> require 'db/migrate/4_test4' # the code above => true irb(main):003:0> Test4.up => ... irb(main):004:0> puts DBMigrator::Database.dump('postgresql') CREATE TABLE sidebars (id serial primary key, controller character varying(255), active_position integer, active_config text, staged_position integer, staged_config text) ; BEGIN; INSERT INTO sidebars ("staged_position", "active_config", "active_position", "controller", "staged_config") VALUES(NULL, NULL, 0, 'category', NULL); COMMIT; BEGIN; INSERT INTO sidebars ("staged_position", "active_config", "active_position", "controller", "staged_config") VALUES(NULL, NULL, 1, 'static', NULL); COMMIT; BEGIN; INSERT INTO sidebars ("staged_position", "active_config", "active_position", "controller", "staged_config") VALUES(NULL, NULL, 2, 'xml', NULL); COMMIT;
Postgres works now, at least with the 4 or 5 examples that I’ve swiped from Typo’s migrations. SQLite and MySQL are nearly working; I think I just need to fake out a couple classes each and they’ll be up and running. Once that’s done, I’ll bundle this all up into a Rails generator so people can do this:
$ ./script/generate schema postgresql create db/schema.postgresql.sql $ ./script/generate schema mysql create db/schema.mysql.sql $ ./script/generate schema sqlite create db/schema.sqlite.sql