PetaPoco - Custom mapping with the Mapper interface

Really like PetaPoco so far, so refreshing. I have a question; do you have any plans to support nested POCOs where a POCO contains another POCO as a property? The convention could be that the name of the nested POCO property matches the name of a joined table in the query, or some kind of alias prefix in the query. This would really help when hydrating domain models where nested POCOS are used for structuring and object reuse. Otherwise my domain models would either have to be very flat or I'd have to write code to hydrate the domain entity from the POCO, both of which I'm reluctant to do

This is the kind of code I would love to see work with PetaPoco, the vat property would be automatically populated :

using System; using System.Collections.Generic; using System.Linq; using System.Text; using PetaPoco;

namespace PetaPocoTest { public class VAT { public string id {get; set;} public string description {get; set;} public double rate {get; set;} }

public class Fund
{
    public long id {get; set;}
    public string description {get; set;}
    public string GLCode {get; set;}
    public VAT vat {get; set;}

    public Fund()
    {
        vat = new VAT();
    }
}

public class Program
{
    static void Main(string[] args)
    {
        var db = new PetaPoco.Database( "GeneralLedgerDatabase");

        // Show all articles    
        foreach( var fund in db.Query<Fund>("SELECT * FROM fund left outer join VAT on VAT.ID = fund.vatid"))
        {
            Console.WriteLine("ID               : {0}", fund.id);
            Console.WriteLine("description      : {0}", fund.description);
            Console.WriteLine("GL code          : {0}", fund.GLCode);
            Console.WriteLine(" vat.id          : {0}", fund.vat.id);
            Console.WriteLine(" vat.description : {0}", fund.vat.description);
            Console.WriteLine(" vat.rate        : {0}", fund.vat.rate);
            Console.WriteLine();
        }
    }
}

}