-------- Original message --------
From: Behrang Saeedzadeh <behrangsa@xxxxxxxxx>
Date: 11/6/19 2:48 AM (GMT-05:00)
To: jpa developer discussions <jpa-dev@xxxxxxxxxxx>
Cc: Bill Shannon <bill.shannon@xxxxxxxxxx>, Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx>, Ivar Grimstad <ivar.grimstad@xxxxxxxxx>, Tanja Obradovic <tanja.obradovic@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [jpa-dev] What's next for JPA?
Hi all
I try to get more engaged here. Right now off the top of my head, I was thinking about discussing the possibility of adding support for UNION to JPQL/Criteria.
It sometime can lead to significant performance improvement as some planners struggle optimizing a query with many joins but do fine when the query is split into two where results are combined using UNION.
Another feature was the possibility of declaring associations with Streams instead of Collections, with semantics that would allow iterating over millions of rows without eating too much memory.
Also now that some RDBMSes have first class support for JSON, letting users inttospect JSON fields and use them in WHERE clauses, adding support to JPQL/Ctiteria would be nice.