most of your issues here are with Datamapper - you may be best to start with AR and sql sessions and then you'll find Merb to be quite stable!!
edraper
· 1 year ago
Absolutely, you're right - however as a Rails guy looking into Merb, one of the most interesting aspects is it's performance, and it's ability to handle requests in a thread-safe manner, improving things like file uploads. Unfortunately, with the "mutex" config option turned off, ActiveRecord isn't usable with Merb currently, and so the natural choice for me, and anyone else interested in getting the best out of Merb at the minute, is probably going to be DataMapper as far as I can see. So the issues I came across, while mostly related to DataMapper, are pertinent really to the whole Merb experience.
However besides what I mentioned in the post, I haven't really run into too many other problems - I definitely think that over time Merb has the potential to become a really powerful framework.
Michael Leung
· 1 year ago
Frazer, I haven't really had that many issues with DataMapper save for the lack of non-destructive migrations. I actually am starting to prefer the syntax of DataMapper to AR. In fact I've always like the Fowler's DataMapper design pattern more than ActiveRecord anyhow.
All Comments
However besides what I mentioned in the post, I haven't really run into too many other problems - I definitely think that over time Merb has the potential to become a really powerful framework.
What kind of problems have you run into use it?