feature request: add BatchCount and StatementCount to CommandLog

we're trying to track down some weird sql generated by LS from our model after some changes. we only noticed it via a sql trace which showed a whole lot of additional sql being generated.

i've written a custom logger which i'm using to assert the number of sql batches/queries being emitted from the unitofwork but it would be a lot easier if you exposed these via the CommandLog. (not to mention a little safer as I'm tying my statementcount to a LS implementation details by tracking statements via terminating commas)
Then it would be even more trivial to write unit tests against the model to assert how many statements/batches are being issued as we enable/change things like eager loading and aggregates.

cheers justin

eg

public abstract class UnitOfWorkTestContext : TestContext
{
protected static readonly IKernel Kernel = new StandardKernel(
    new NLogModule(),
    new LazyModule(),
    new ModelModule<MyUnitOfWork>("MyConnStr", () => new SystemAuditInfoStrategy("UnitTests")));

static TransactionScope transactionScope;
protected static MyUnitOfWork sut;
protected static LightspeedSqlAuditingLogger sqlAuditingLogger;

Establish context = () =>
    {
        var lightSpeedContext = Kernel.Get<LightSpeedContext<MyUnitOfWork>>();
        sqlAuditingLogger = new LightspeedSqlAuditingLogger();
        transactionScope = new TransactionScope();
        sut = lightSpeedContext.CreateUnitOfWork();
        sut.Context.Logger = sqlAuditingLogger;
    };

Cleanup afterwards = () =>
    {
        sut.Dispose();
        transactionScope.Dispose();
    };
}

public class when_doing_something : UnitOfWorkTestContext
{
static Entity entity;
static EntityCollection<EntityB> entityBs;

Establish context = () =>
    {
        entity = sut.FindById<Entity>(new Guid("B059AF87-3498-4FB1-949B-A01300E9D34E"));
        sqlAuditingLogger.Clear();
    };

Because of = () => 
    exception = Catch.Exception(() => 
        entityBs = entity.EntityBs);

It should_execute_a_single_sql_batch = () => 
    sqlAuditingLogger.BatchCount.ShouldEqual(1);

It should_execute_a_single_sql_query = () => 
    sqlAuditingLogger.StatementCount.ShouldEqual(1);

It should_not_throw_an_exception = () => 
    exception.ShouldBeNull();
}

public class LightspeedSqlAuditingLogger : ILogger
{
public int BatchCount { get; private set; }
public int StatementCount{ get; private set; }
const string SqlStatementPattern = @"\;";
static readonly Regex SqlStatementRegex = new Regex(SqlStatementPattern);

public void LogSql(object sql) {
    BatchCount++;
    CommandLog commandLog = sql as CommandLog;
    if (commandLog == null) {
        return;
    }

    var stmtCount = SqlStatementRegex.Matches(commandLog.CommandText).Count;
    StatementCount += stmtCount;
    Console.WriteLine(commandLog.CommandText);
}

public void LogDebug(object text) {
    // do nothing
}

public void Clear() {
    SqlBatchesIssued = 0;
}
}

As far as I know, a CommandLog object always represents exactly one batch. (It represents one IDbCommand, which is effectively what a batch is.) So there's no point adding a BatchCount property.

I'll see if we can capture the statement count, but it's a bit tricky with our current architecture, so no promises.