Hi cremor, I actually took a look at your pull request last night - reason being that it affects several issues, has a priority of Critical, and you have provided tests and a pull request. I will continue looking at it for 3.3.
Running the tests you provided against SQL Server doesn't fail, but I think you mentioned the issue can be reproduced with SQLite, so I will try that next. On 20 February 2012 15:17, cremor <[email protected]> wrote: > > One question is if there remains any open issues that *MUST* be fixed in > 3.3.0? > > You might see that differently because I'm actually affected by the > bug, but in my opinion my open pull request is an essential fix: > https://github.com/nhibernate/nhibernate-core/pull/55 > > If one is affected by this bug, an exception is thrown, so it is > critical in my opinion. And the fix is quite simple. > And it fixes 3 JIRA issues ;-) > > On Feb 17, 10:52 am, Oskar Berggren <[email protected]> wrote: > > 2012/2/17 nfplee <[email protected]>: > > > > > Hi, i was wondering when 3.3.0 is due? I ask because it's been a long > > > time since version 3.2 was released and version 3.3 addresses alot of > > > the issues (mainly with the LINQ provider) that prevented me from > > > upgrading a site which uses version 2.x. Sorry to seem pushy but i've > > > been delaying this project for quite a while now and my client is > > > being to get inpatient. > > > > No exact date has been set, but the consensus when last discussed was > > that it should be soon. > > > > One question is if there remains any open issues that *MUST* be fixed in > 3.3.0? > > > > Another thing, if you haven't done so already it would be great if you > > could do the upgrade to the current preliminary 3.3.0 trunk, to see if > > the current state will work for your project or if there are > > regressions or issues that will still be a problem. > > > > /Oskar >
