Add support to null parameters in stored procedures (fix issues #245 and #274)
Merge pull request #287 from CaioProiete/add-support-null-params-in-stored-procs

Add support to null parameters in stored procedures (fix issues #245 and #274)
INCR to v3.9.56
INCR to v3.9.57
Don't break loop on NullReferenceException. ...

Without this, the exception is caught in the PopulateWithSqlReader
function and terminates the loop, leaving all columns that appear after
the problematic column to their default values.

We catch the NullReferenceException when we attempt to set the value
instead of allowing it to propagate to the column loop so that only the
problematic column will be left inept.
Merge pull request #289 from sjuxax/master

Don't break loop on NullReferenceException. ...
Support for CommandTimeout

Support for CommandTimeout
Add SqliteOrmLiteDialectProviderBase.ParseViaFramework option
fix whitespace
Add some fall-back guesses when mapping between datareader and object to better support legacy databases

This is very useful when querying legacy databases that cannot be changed (views, stored procedures, ...)
that contains fields with underscores and/or special characters and/or prefixes that either wouldn't be
possible to be declared in C#, or wouldn't comply with standard naming conventions

Examples of mappings that are now possible with this change:
[Database]       [C#]
customer_id   => public int CustomerId { get; set; }
quantity_%    => public decimal Quantity { get; set; }
t040_name     => public string Name { get; set; }
Merge pull request #291 from CaioProiete/improve-mappings-for-legacy-databases

Add some fall-back guesses when mapping between datareader and object to better support legacy databases
Support PostgreSQL functions with integer and string array arguments.
Merge pull request #292 from jeffgabhart/pgsql/func-array-arg

Support PostgreSQL functions with integer and string array arguments.
Update README.md
updated FirebirdTests to fix transactions use.

It seems that the FirebirdTest project is outdated, and Transaction
didn't work.
It had to do with the way connections were initialized.

Changed:
using (var db = ConnectionString.OpenDbConnection())
To:
using (var db = new OrmLiteConnectionFactory(ConnectionString,
FirebirdDialect.Provider).Open())

With this change the Firebird provider works as expected, at least
regarding the use of Transactions.
Also added app.config and changed
OrmLiteTestBase.GetFileConnectionString() to use it, to allow an easy
connection string setup.

Only remaining problem now is at
OrmLiteQueryTest.Can_select_with_filter_from_ModelWithOnlyStringFields_table().
db.ByExampleWhere() doesn't ignore NULL properties and the query returns
0 rows.
Merge pull request #294 from madaleno/master

updated FirebirdTests to fix transactions use.
Update README.md
Added overloaded ByExampleWhere<T>() method

Added overloaded ByExampleWhere<T>(this IDbConnection dbConn, object
anonType, bool excludeNulls) because OrmLiteQueryTests that used
ByExample were failing.

Passing the excludeNulls all the way allows for the correct sql
statement to be generated.
In this case not having the where clause with null value properties
which is what the test expects anyway.
Merge pull request #295 from madaleno/master

Add overloaded ByExampleWhere<T>() method with excludeNulls parameter
added schema prefix to JoinSqlBuilder for building queries