JPQL native syntax for date/time literals

[gavinking]

trafficstars

This came up in #391.

Currently, JPQL has no native syntax for date/time literals, and just piggy-backs off the JDBC escape syntax. This syntax is kinda ugly and looks visually out-of-place in a JPQL query.

We recently added a native syntax for this to HQL, it's documented here:

https://docs.jboss.org/hibernate/orm/6.3/querylanguage/html_single/Hibernate_Query_Language.html#datetime-literals

I think it would be nice to add some subset of this to the spec.

Thoughts?

[trajano]

Braced primarily because it is shortest among them. Not only that you can tell when it ends unlike the third one. Question is how do we handle ZonedDateTime and Instant but it may be implicit with OffsetDateTime already.

The thing you need to make sure of is the capability of passing it with a Z timezone. The other thing to watch out for is the MIN and MAX values for Instant and ZonedDateTime are different.

[gavinking]

Braced primarily because it is shortest among them.

It's short, but it's also the option that looks most out of place in the SQL-like syntax. I personally don't find it aesthetically appealing, though of course others are free to disagree.

Not only that you can tell when it ends unlike the third one.

This is an advantage indeed.

[gavinking]

Question is how do we handle ZonedDateTime and Instant but it may be implicit with OffsetDateTime already.

I don't think we actually need Instant literals, all you would need is an implicit conversion from OffsetDateTime to Instant.

That said, I do still think that having the type stated explicitly, as in date 2000-12-3 is a weak advantage.

[trajano]

The closest thing to SQL is literally '

That is '2023-08-14' and having the JPQL know that the target the type LocalDate and perform the necessary. However, I still prefer { } because it opens up the possibility of other things lets say

• UUID
• semantic versions {2.0.5} // I don't think any database supports that
• geo data such as {-77.00, 55.00} representing latitude and longitude
• A period { 2023-08-14 to 2023-08-30 }
• A duration { 16 days }

[gavinking]

Right, this is an argument that @sebersole also makes.

[trajano]

Which one @gavinking the use of ' or the additional representations possible

[gavinking]

Your point about { .... } being generalizable to other types.