http://persumi.com/u/fredwu/tech/e/blog/t/schema Persumi - Level up your writing and blogging with AI Blog Tech Sat, 16 May 2026 04:50:54 +0000 Thu, 22 Jul 2010 12:30:50 +0000 http://persumi.com/u/fredwu/tech/e/blog/p/rails-introducing-datamappify-activerecord-without-db-migrations http://persumi.com/u/fredwu/tech/e/blog/p/rails-introducing-datamappify-activerecord-without-db-migrations Blog Tech ifredwu@gmail.com (Fred Wu) <![CDATA[<h2> Introduction</h2> <p> ActiveRecord is without doubt the <em>de facto</em> ORM library for Rails and many Ruby web frameworks. Many developers however, do not like database migrations and prefer to use DSL for data mapping. Datamappify is created with the sole purpose of getting rid of the DB migration headaches.</p> <h2> Why Not DB Migrations?</h2> <p> Well, depending on your specific project, DB migrations might create more trouble than it’s worth. Besides, your code is already version controlled, so why create a separate version control for your DB schema?</p> <h2> Why Not Use DataMapper, Sequel, etc?</h2> <p> As stated in the introduction, ActiveRecord is the most popular ORM in the rails community, it is actively developed and battle-tested. If your only grief with ActiveRecord is the DB migrations, why not just eliminate it be happy? ;)</p> <p> <strong><a href="http://github.com/fredwu/datamappify">Go check out the code</a>!</strong></p> ]]> http://persumi.com/u/fredwu/tech/e/blog/p/rails-introducing-datamappify-activerecord-without-db-migrations