DBIC is simpler than SQLAlchemy, so it doesn't do this kind of thing for you. Personally, I like the obvious separation of the objects: It makes the data model and relationships more apparent from the code (though I would remove the user_ prefix from the relationships). I've rarely had all of my code (DBIC or SQLAlchemy) survive database schema changes, unless I had planned for that schema to change (simple adding/removing optional columns for example).
|Replies are listed 'Best First'.|
Re^4: Search for ORM with Multi-Table-Object Support
by Xel (Novice) on May 03, 2012 at 07:10 UTC