[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jpa-dev] Persistence.NEXT
|
Hi,
here are some ideas:
- Make use of Jakarta Config for configuring JPA properties. We
could define interfaces that contain methods for all the JPA
configuration properties. Implementations would then read the
configuration through that mechanism, if the Config API is on
the classpath. This could allow making the persistence.xml
optional.
- If the supported Java version is upgraded to 17, we could
specify that record classes are valid types to use for
embeddable types.
- Add support for some SQL constructs: subquery in FROM clause,
WITH clause, window functions and ordered set aggregate
functions (e.g. listagg), tuples/row value constructor
- Continue standardizing some SQL functions: extract, format,
truncate, left/right, replace, collate, octet_length,
pi/radians/degrees, log, tan/sin/cos, tanh/sinh/cosh,
atan/atan2/asin/acos, atanh/asinh/acosh, cot/sec/csc
Overall, I don't think we are in need of a new major version.
Regards,
Christian
Am 04.04.2023 um 15:02 schrieb Lukas
Jungmann:
Hi,
with ongoing Jakarta EE 11 planning[1] (discussion[2]), what do
you think the Persistence specification should aim for?
Do we want to provide minor, incremental update to the
persistence specification OR is there a preference to do major
update giving us an opportunity to do bigger and possibly also
some breaking changes?
Thanks,
--lukas
[1]:
https://jakartaee.github.io/jakartaee-platform/jakartaee11/JakartaEE11ReleasePlan
[2]:
https://docs.google.com/document/d/1m-dkvbL0iFFzitO4vt1SVq6GGSJyFdCDM2NU_FzGS10/edit#heading=h.1oyn459kodrn
_______________________________________________
jpa-dev mailing list
jpa-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jpa-dev
