Yoann Rodière 6f6874b8cf HHH-14124 Avoid too many list allocations when hydrating query results ...

I suspect the original goal of having a single list of hydrated objects
for all rows was to avoid instantiating one list per row, but we did
just that in the fix in the last commit.

This introduces a hack to signal that we're starting to process a new
row while still keeping a flat, single-list structure: we inserting
null elements in the list of hydrated objects.

This is admittedly very ugly, but it's the only solution I can come up
with if we want to keep the number of memory allocations similar to what
we used to have. And hopefully this code will disappear in ORM 6.0.

2020-07-30 13:34:41 +01:00

..

src

HHH-14124 Avoid too many list allocations when hydrating query results

2020-07-30 13:34:41 +01:00

hibernate-core.gradle

HHH-14033 - SQL script parsing problem with multi-line comments

2020-05-19 12:25:34 -05:00