Another Sequel user here, very happy. The only thing I'd like to see would be a more flexible object mapping layer on top of the relational core. Something alo

Another Sequel user here, very happy. The only thing I'd like to see would be a more flexible object mapping layer on top of the relational core. Something along the lines of Python's SQLAlchemy. Sequel::Model is a simple ActiveRecord-style ORM layer (in the sense of Fowler's ActiveRecord pattern) and in a way is very flexible, if you don't mind implementing a bunch of lower-level hooks for certain things. But sometimes you do want a more heavyweight session-based approach where you have an object model with a bunch of associations, a flexibly-configured mapping of that object model to the database, and an ORM which knows how to take a batch of changes to the object graph and commit them to the database in one transaction. Still yet to see a tool like this for ruby, but I think sequel could be a good foundation for it.