What's new in re-linq 1.15.15.0
May 7, 2014
- New feature:
- Enable Portable Class Library profile for Windows Phone 8.1
New in re-linq 1.15.13.0 (Apr 23, 2014)
- New features:
- Support for SQL Server 2014
- Support for Portable Class Library in Remotion.Linq assembly
- Changed:
- Changed Exception thrown by types derived from MethodCallExpressionNodeBase in case not-supported Resolve-opertion from InvalidOperationException to NotSupportedException
- Changed Exception thrown by ResultOperatorBase in case of a type mismatch from InvalidOperationException to ArgumentException
- It is no longer supported to register query operators that are only distinguishable via a parameter whose type is a generic parameter of the declaring type
- Added flag to MethodInfoBasedNodeTypeRegistry.GetRegisterableMethodDefinition(...) to select how to handle ambiguous method definitions on geniric types
- API-changes to Remotion.Linq.ReflectionUtility
New in re-linq 1.15.7.0 (Dec 30, 2013)
- Changes:
- SeparatedStringBuilder is obsolete
- Dropped ArgumentTypeException
- Dropped ArgumentEmptyException
New in re-linq 1.15.2.0 (Jul 11, 2013)
- Changed:
- Removed ExtensionExpression.Reduce() and ExtensionExpression.ReduceAndCheck() methods
New in re-linq 1.15.1.0 (Jun 24, 2013)
- New Features:
- Support the conditional expressions with type in ExpressionTreeVisitor.VisitConditionalExpression
- Fixed:
- "Argument types do not match" is thrown when processing raw Expression.
- Other changes:
- Removed ExtensionExpression.Reduce() and ExtensionExpression.ReduceAndCheck() methods
New in re-linq 1.13.196.0 (Apr 27, 2013)
- Performance:
- SQL Backend - Optimize away left outer join when accessing the primary key property of a relation property when the foreign key is on the left side of the relation
- New feature:
- SQL Backend - Support complex identity for entity expressions
- Changed:
- SQL Backend - No left outer join is generated when accessing the primary key property of a relation property when the foreign key is on the left side of the relation
New in re-linq 1.13.194.0 (Apr 11, 2013)
- New Feature:
- SQL Server 2012 Support
New in re-linq 1.13.183 (Jan 26, 2013)
- New feature:
- SQL Backend: Support for local method calls
New in re-linq 1.13.180 (Dec 31, 2012)
- New features:
- SQL Backend: Support DateTime.Add... functions
- Allow casts in eager fetch result operators
- Add a way to transform MethodCallExpressions via a custom attribute applied to the method
- Changes:
- SQL Backend: MethodCallTransformerAttribute and IMethodCallTransformerAttribute have benn replaced
New in re-linq 1.13.179 (Dec 18, 2012)
- Fixed:
- Different query models for similar semantical queries
- SQL Backend: GroupResultOperator doesn't work correctly after a Take result operator when the grouping key involves an implicit join
New in re-linq 1.13.178 (Dec 10, 2012)
- New:
- SQL Backend: Reduce the number of parameters generated when translating complex string manipulation functions or nullable boolean conversions
- Fixed:
- Assembly version is not getting updated
New in re-linq 1.13.177 (Dec 3, 2012)
- Remove public JetBrains.Annotations attributes from re-linq assemblies
- SQL Backend: Support nullable booleans
New in re-linq 1.13.171 (Oct 19, 2012)
- Support empty parameter names when parsing lambda expressions
- SQL Backend: An InvalidOperationException is thrown when an Equals method call is made with objects of different static types
- SQL Backend: Potential Bug: MemberAccessResolver swallows NamedExpressions
New in re-linq 1.13.170 (Oct 13, 2012)
- Allow and deal with exceptions within partial evaluation
- Comparing compound values for inequality causes an incorrect comparison to be emitted
- SqlContextExpressionVisitor doesn't handle LambdaExpressions and InvocationExpressions correctly
- Relinq breaks on parsing null values
- IDictionary.Contains should not be translated to a ContainsResultOperator
- UnionResultOperator should act as a query source for following query operators