added support for schema changes - schema can now change and dapper will re-generate the deserializers.

salt the earth if we start getting multiple errors; the risk here is that it is a schema change that impacts multiple queries

EG:

  DynamicParameters p = new DynamicParameters();
  p.AddDynamicParams(new { A = 1, B = 2 });
  p.AddDynamicParams(new { C = 3, D = 4 });

Expose some more of dapper's internals

Dapper.Contrib Insert Fails

smarter param filtering ... note dapper does not support non-ascii named params nicely. the filtering will be a bit wonky

--HG--
rename : Dapper.Contrib/Extensions/SqlMapperExtensions.cs => Dapper.Contrib/SqlMapperExtensions.cs