On Wed, Jun 16, 2010 at 11:20 PM, Dan Kubb (dkubb) <dan.kubb / gmail.com> wrote:
>> I've ranted about this elsewhere, so I'll keep this short, but I urge you to not be misled by the word "legacy."
>
> This thread was started by someone having problems using an ORM with a
> legacy schema, so that's what we've been discussing mostly. However,
> this problem can be more generally classified as an issue with
> controlling the mapping between an existing schema and ruby classes.

Actually my main problem isn't the legacy schema, it's datamapper's
behaviour when something doesn't save. It makes debugging during
development really hard unless I put a begin/rescue or if/then block
around every db write.

martin