I haven't been setting my issue priorities correctly, and I can't seem
to change them after the issue has been created. Additionally, a
number of "bugs" I filed turned into patches as I had time. Here's a
list of issues and what I think they should be at.
NH-2402 [PATCH] LINQ equality should map to SQL equality (Also
fixes NH-2398, NH-2397, and others not reported by me.)
This patch is of high priority as it would cause breaking changes
if applied after the release. There have been no official releases
with the current behavior, so there's nothing to officially break yet.
Resolves a number of issues in JIRA.
NH-2392 [PATCH] ICompositeUserType support for cases where not
all parameters should be set (such as dynamic-update)
This is a breaking change that was discussed earlier this week on
the mailing list. When using immutable types, I don't see an easy
work-around. It's clear that the interface needs to change at some
point; better to get the breaking change into the major release. The
internal changes are low risk here.
NH-2394 [PATCH] Comparing an enum (stored as a string with a
user type) to an enum literal fails
Very useful patch that derives the types of linq parameters from
what they're being compared to. Would resolve a number of major
priority issues already in JIRA.
NH-2403 [PATCH] Linq boolean constants are of wrong type (integer)
Tiny patch, fixes some parts of Linq for databases that don't use
integers for bools (like PostgreSQL).
NH-2318 [PATCH] Template functions fail with certain
combinations of arguments.
Quite useful with Linq for creating methods that can do things like:
MSSQL: (a is null and b is null) or (a is not null and b is
not null and a = b)
PostgreSQL: a is not distinct from b
MySQL: a <=> b
Not as important if "null equality" is ignored for the 3.0 release.
NH-2401 [IMPROVEMENT] Method for specifying IType of LINQ parameter
Can wait until a point release IMHO. The changes would be small
and low risk, so no big deal in any case.
I was a little surprised how quickly I ran into issues with the new
LINQ provider. We had only a handful of LINQ queries utilizing
NHibernate.Linq previously, but even those broke with the new one. In
any case, I hope these patches will make a significant dent in the
work needed on the Linq provider.
Okay, that's it for now. :)
Patrick Earl
