We all discussed these changes in the dev list. You could easily have been
proactive in these concerns. And yes, I mentioned exactly these points
Sanne is bringing up on that original discussion.
Bottom line we all agreed that there were some breaking changes in 5.2 and
we all understood the mot
On 20 June 2016 at 12:03, Gunnar Morling wrote:
> What changes are we talking here specifically? Have they been done
> intentionally or by accident?
The change with highest impact on Search is that the various Query API
interfaces have been moved.
The legacy contracts still exist in the original
What changes are we talking here specifically? Have they been done
intentionally or by accident?
For the better or worse, ORM - so far - doesn't stick to SemVer rules, so I
don't think we should revert anything which has been changed on purpose.
Different story for accidental changes of course.
I
On 20 June 2016 at 08:33, Emmanuel Bernard wrote:
> Are the incompatibilities here for good on ORM, or could they be
> reverted / softened in the 5.2 branch to allow for an easier path?
I'm working on a set of PRs for both ORM and Search which reduce the
list of incompatibilities,
but while the a
On 06/18/2016 06:14 PM, Steve Ebersole wrote:
> TIMESTAMP is a deprecated synonym for the TSQL rownumber datatype, at least
> on SQL Server. Not sure specifically about Sybase. So I'll use "rownumber"
> here...
>
> As we discussed in HipChat yesterday OptimisticCacheSource was added a long
> time
Are the incompatibilities here for good on ORM, or could they be
reverted / softened in the 5.2 branch to allow for an easier path?
On Tue 2016-06-14 17:33, Sanne Grinovero wrote:
> There have been various complaints that people can't upgrade to the
> latest Hibernate ORM because they don't have
