Added support for ICustomQueryParameters to be members of a dictionary that can then be passed into a new DynamicParameters object.

Generally, working with an IDictionary<string,object> and DynamicParameters has worked well.  However, when one of the entries in the dictionary is an ICustomQueryParameter, it would blow up in the SqlMapper.LookupDbType method.  This allows parameters that are part of a dictionary to simply call 'AddParameter' passing in the command and name.

Dapper.Contrib - Fix broken properties cache.

Fix double?/decimal? conversions (with test); added (currently failing; acknowledges current state) test re missing members

Signed-off-by: Marc Gravell <marc.gravell@gmail.com>

- huge thanks to bkaid

Added support for TVP in anonymous objects

DapperRow dynamic invocation fails in Visual basic - fix

Implement connection-string equivalence (similar to https://github.com/SamSaffron/dapper-dot-net/pull/80)

Fix Issue131

@david.obando

Rainbow: Ignore Id property when calling Table.Insert 

Updated Table methods to better support multi-DB

"Id" is being removed most places in Rainbow, but not on Table.Insert. I
changed this to make it consistent with SqlCompactTable.Insert and
Table.Update.

Fixed DapperTable issue

Added database schema support to Dapper.Rainbow

Bug fix for "Invalid attempt to call MetaData when reader is closed"

Added possibility to add custom type maps - enables serialization of enums to DbType.String instead of DbType.Int32

Would occasionally generate exception "Invalid attempt to call MetaData when reader is closed"

Allows a class to have a reserved word as a column name.

This fixes a bug found in CS 51509960 where the following sequence would
result in an InvalidOperationException being thrown due to an attempt to
access a disposed of DataReader:

- Perform a dynamic query that yields no results
- Add data to the source of that query
- Perform a the same query again

Insert failed when a word such as order was used as a column name.
Added [] around the column name.

Also modified the test for InsertGetUpdate().  The first Get is now a
User instead of IUser.  There is some bug where using the interface
twice first on a null result and then on the real result causes the
reader to not be open when trying to map the type.

No sense in escaping TableName only for update, "from" isn't universally
optional for deletes, First() should be virtual to allow alternatives to
TOP 1