From: Dan Kubb Date: 2010-06-16T05:00:08+09:00 Subject: Re: datamapper blues Richard, > In practice I have found it a challenge to make DataMapper conform to legacy schema, and error feedback was limited. This is great feedback to have, and precisely the kind of information I need in order to improve DataMapper. Now that DM 1.0 is out, and the API is stable, DM is shifting the focus a bit. One of the primary areas I want to improve is legacy schema mapping, since I think that's a bigger issue than we'd like to admit in the ruby world. Most projects are not beautiful "green field" apps. Almost every company has legacy systems that sit in the corner, and programmers dread having to work on them. They would love to use ActiveRecord with the schema and talk to it using ruby, except AR makes too many assumptions about the schema. Even if it does work, the 1:1 mapping of columns to attributes can make for some ugly ruby code. As the maintainer of DataMapper I want to help solve this problem, or at least make it less painful. Even if we partially solve it and someone else extends that work I'm cool with that too. At the very least I am going to give it a good try. There are *so* many developers who would love to use Ruby, but aren't able to because the more "mainstream" tools don't work for them. Richard, I would love to hear more about the problems you ran into using DM with a legacy DB, whether it's here or on the datamapper mailing list. -- Dan --- frmsrcurl: http://compgroups.net/comp.lang.ruby/datamapper-blues