Quote Originally Posted by Ren View Post
Being able to map a handwritten query into objects
I've been playing around with this as well. Mostly it involves using the load() method of related mappers so that, for example, you could load a Post and it's related User in one query, but delegate the mapping into a User object to the UserMapper. I think that's a fine solution (the alternative is mapping both objects in the same class, which would lead to duplication of mappings) for objects that are directly associated with the main object, but I don't know how things would work if you're querying for data for objects several relations down the line.

Also, oddz is right in the use of aliases. Our current mapper code allows use of aliases for selected columns on joined data. I wonder if it might be useful to specify a prefix for all columns from a joined table? That might make writing mappings that span several tables a little easier.