Ruby on Rails makes it easy to bootstrap a greenfield project. Unfortunately not all projects are greenfield, so sometimes you need to work with a legacy database schema. ActiveRecord is a great choice when you have a full control over your database from the very beginning, but what should you do if you need to connect to a database with a schema that isn’t in-line with Rails conventions?
DataMapper Core Contributor and Aquo team member, Piotr Solnica, has written a great blog post for our partner Engine Yard entitled Using DataMapper and Rails with Legacy Schemas. Read it and you can say goodbye to your fear of inheriting a legacy app.