[hibernate-dev] Query#iterate
Christian Beikov
christian.beikov at gmail.com
Fri Jan 27 10:50:27 EST 2017
I just know of people that are using iterate() now for efficient
incremental processing, but I guess any other approach(streams maybe?)
to do incremental processing would be good enough for these users.
Unfortunately I don't know what a shallow query is or what the
implication on the query or the processing of being shallow are.
I guess this has to do with how row processing is done? I can imagine
that this complicates the implementation, but really, there are users
out there which rely on the performance model of that.
Am 27.01.2017 um 15:42 schrieb Steve Ebersole:
> I know I started a discussion of this somewhere with some of you, but I
> cannot find it anymore.
>
> I had suggested we consider getting rid of this Query#iterate method. I
> just wanted to get everyone's opinions of this. Specifically, getting of
> it in 6.0.
>
> If anyone has dug much into the current Antlr 2 based parser you will be
> familiar with this idea of shallow versus non-shallow queries. That is
> where this comes into play. Query#iterate is a shallow query
> (shallow=true). All other queries are non-shallow.
>
> There are quite a few internal reasons to simply drop that method and get
> rid of the idea of this shallow flag. I am happy to discuss these reasons
> for those interested and that do not know.
>
> But obviously we should not be getting rid of things just because of
> "internal complications" if they are used by many users. I cannot speak to
> whether any users use this, let alone how many.
>
> Thoughts?
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
More information about the hibernate-dev
mailing list