I was wondering where Lotus went. They haven't done associations yet. Maybe the length of time for them to get that done answers part of my question.
They take a strong DDD view with repositories. I find DDD interesting but not sure I want to be forced into it by my ORM. On Monday, March 28, 2016 at 12:20:55 PM UTC-6, Jeremy Evans wrote: > > On Monday, March 28, 2016 at 11:15:55 AM UTC-7, Brady Wied wrote: >> >> My first instinct is a hell of a lot more than I'm expecting but I'm >> thinking about it. >> >> Here are the components I can think of (to achieve domain models free of >> persistence logic): >> >> 1. Mapping DSL a la Fluent NHibernate >> 2. Plugin to convert Sequel datasets to the domain models (perhaps >> like model/base.rb's def call(values) method) >> 3. Code that uses proxy collections for the domain model associations >> to allow lazy loading, etc. >> 4. Identity map - would have to revive this. I think this wouldn't be >> required if I exclude support for reuniting "detached objects" in the >> Hibernate sense of the word >> >> It might be easier to do this by treating Sequel models as "mapper" >> classes and then converting them, but I'm not sure. >> >> ROM is sort of interesting to me but I think they are trying to do >> something a lot different (CQRS by default, etc.) than what I want. I >> really want what NHibernate gives me (mapped persistence with the >> appearance of in memory access). >> >> Does anyone have any thoughts about this? Foolish idea? >> > > You can look at Hanami::Model, it is an attempt to build a data mapper on > top of Sequel: https://github.com/hanami/model > > Thanks, > Jeremy > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
