Enterprise Library Data Acccess Application Block Implementation using Teradata .Net Provider

Has anybody tried extending the Enterprise Libraray Data Access Application Block so that it works with the Teradata .Net Provider?
To get things up and running, my prototype extends the abstract Database class and passes TdFactory as a constructor argument..  

using System;
using Microsoft.Practices.EnterpriseLibrary.Data;
using Teradata.Client.Provider;

namespace Common.Database
{
    public class TeradataDatabase : Microsoft.Practices.EnterpriseLibrary.Data.Database
    {
        public TeradataDatabase(String conectionString) : base (conectionString,new TdFactory())
        {            
        }

        protected override void DeriveParameters(System.Data.Common.DbCommand discoveryCommand)
        {
            throw new NotImplementedException();
        }
    }
}

 
Still working on implementing Teradata-specific stuff, like mapping to TdType and other optimization stuff..
 
Wondering if anybody has done any research or has sample code related to this solution..  Any pros/cons of using Ent Lib Daab with Teradata .Net provider in terms of performance, compatability, etc..