Stream result change proposal
by Vlad Mihalcea
Hi,
While writing documentation for the new 5.2 Query.stream() API, I realized
that we don't return a Stream<T>, but a Stream<Object[]> which could
confuse users.
This is because ScrollableResultsImpl does something like this:
if ( result != null && result.getClass().isArray() ) {
currentRow = (Object[]) result;
}
else {
currentRow = new Object[] {result};
}
The result is the actual entity that we queries, while the currentRow
is an Object[].
I think we might want to change the stream result so that we return
the result for each available entry.
Vlad
9 years, 9 months
UserType backward incompatibility in 5.2
by Vlad Mihalcea
Hi,
I think that HEM introduced a backward incompatibility for UserTypes
because the contract has changed for nullSafeGet and nullSafeSet.
Instead of a SessionImplementor, we now need to provide a
SharedSessionContractImplementor.
This is going to break all UserTypes classes that were implemented by our
users.
Is this issue known?
Vlad
9 years, 9 months
5.1 branch backporting
by Vlad Mihalcea
Hi,
I have backported some fixed to 5.1, and I'm not sure if that was the right
thing to do.
I know that for 5.0 we should ask Gail if to backport anything
Now that we moved to 5.2, should we also ask Gail when to backport
something to 5.1 too?
Vlad
9 years, 9 months
