Shaolinq.SqlServer 1.8.10.1416-fix-distinct-count-b

• • Shaolinq (>= 1.8.10.1416-fix-distinct-count-b)

# 1.8.10
- Fixed SQL Server unique index null handling ANSI compliance shouldn't include primary keys because they're not nullable.
# 1.8.9
- Fixed SQL Server unique index null handling ANSI compliance not always inserting index filter for null checks on columns foreign key columns.
# 1.8.8
- Fixed bool properties not being handled like other types when excluding a property from an index to support null-ansi-compliance.
- Ignore non-nullable columns when injecting conditions to exclude null values from a unique index in SQL server (for null-ansi-compliance).
# 1.8.7
- SQL Server provider null-ansi-compliance support whereby null values are excluded from unique indexes by means of a check for not null now excludes this check for properties that are explicitly referenced within the user-defined index condition (if a user-defined index condition is specified).
# 1.8.6
- Fixed SizeConstraintAttribute placed direectly on an enum type doesn't get inherited
by properties of that enum type if the property is nullable.
# 1.8.5
- Fixed NamingTransformsConfiguration.UniqueIndexConstraintName should default to using NamingTransformsConfiguration.IndexConstraintName before falling to default.
# 1.8.4
- Support defining naming transform for unique indexes (NamingTransformsConfiguration.UniqueIndexConstraintName).
- Added IndexNamesShouldIncludeIncludedProperties option to allow including the names of IncludeOnly properties in the name of indexes.
# 1.8.3
- Fix expressions (IndexAttribute.Condition, ComputedMember.GetExpression, ComputedMember.SetExpression) throwing exception when trying to call methods with overloads.
# 1.8.2
- Better support for parsing IndexAttribute.Condition, ComputedMemberAttribute.GetExpression, ComputedMemberAttribute.SetExpression
- Fix IndexAttribute.Condition not included in schema if index is applied at the class level
# 1.8.1
- Fix GetReference sometimes not working between different types that use the same primary key type.
# 1.8.0
- Major bug fix release
- Better support for conditions and and selects involving aggregate calls on recursively related objects projected off recursively related object collections
- Fixed some object sometimes returned multiple times if using Include() with related object collections
- Fixed sometimes less objects than expected are returned when Skip/Take is used in combination with Include() with related object collections
- General improvements to Include() support
- Added overloads to RelatedDataAccessObjects.Items() method - support loading from a new query if eager loaded items aren't available