fixed issue with update alias-parameterized (broken tests:Can_execute_updateParam_using_aliased_columns)
Merge pull request #278 from kaza/master

solves issue with UpdateParam of columns with alias
Change Sql.In to work as expected
fixed filtering with anonymous types and aliases

changed SetParemeter in OrmLiteReadExtensions
to handle the conversion to aliased field names
when filtering using anonymous type declarations
which reference the original field name
Merge pull request #284 from mishfit/master

Fixed Filtering with Anonymous Types and Aliased Field Names
Question if this kind of predicate is acceptable in extensions?

More of a question than a commit - Is this kind of predicate acceptable in the extensions? If so I'll complete them out. (Basically a wrapper in a sense on select<T>(Predicate) - It just made the code more self-documenting on my end)
Merge pull request #285 from MarkWalls/patch-2

Question if this kind of predicate is acceptable in extensions?
fix sql contains and in expression visitors to allow for value types
Merge pull request #286 from Rfvgyhn/master

fix sql contains and in expression visitors to allow for value types
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