<< I have to wonder if this was done on purpose as a sort
of sabotage, since there is this religious war going on with Merb and
Wow, that’s some serious accusations there.
First off, DataMapper is not developed by the Merb team. do_sqlite3 is
a separate driver letting you use DM and Sqlite3. In the Rails world,
ActiveRecord deals with the various drivers by knowing a lot about
them and their APIs. In the DataMapper world, the drivers were re
written to match the DataObject API (so DM doesn’t have to figure out
how each adapter/driver works).
If the problem you’re having can be reproduced that means few things.
First, you wouldn’t be able to use ActiveRecord/Rails and DataMapper
on the same system using Sqlite3. DataMapper is used by other
frameworks/scripts than Merb and some people even hack Rails to use
DM. Secondly ActiveRecord nor DM should touch sqlite3 so it seems
pretty strange. On windows, both frameworks do require a sqlite3.dll
to be available on the system and they might fight over which version
to use but you seem to be on MacOSX.
Regarding the “religious war” you are referring to, I don’t know why
you say that. As a Merb team member I can assure you that there is not
such a thing. We do not agree on the way Rails does few things, but
there is no war. And it is certainly not something personal. As
mentioned before, we have a lot of respect for DHH and the rest of the
Rails team. Without them, I wouldn’t do what I do now and Merb would
not even exist. So, please don’t mention some crazy sabotage theories
and maybe people will stop thinking that there is a war going on.
Finally, while I was replying to your messages, I installed Rails
2.2.2, upgraded mongrel to 1.1.5 and made sure I was on DM 0.9.7 with
do_sqlite3 0.9.7 and I can’t reproduce your problem.
If you upload a test app, I’d be glad to look at it and try to figure
out what’s going on.