I know, off course, that there is an implementation of the active record
pattern available. And for using it with Rails for tasks of midrange
complexity I consider it to be perfect.
But since this aproach suffers from some limitations, I would like to
know if there are efforts on the way to build a fully featured
I would prefer having it done this way because of the following problems
in my daily work:
No control over the database layout (this is supposed to happen very
Business logic far beyond the point of CRUD operations
I don’t want to have database like operations (i.e save) in the domain
code, all I want there is sending the commit/abort signal to the Unit of
Work. I want to be totaly indepent from the database. This feels more
“correct” to me.
Who knows something about this subject, or is there a better place for a
discussion about it?