Re: [hibernate-dev] How to deal with a constant in CriteriaQuery

That's a possibility indeed, but there will most likely always be some nice function that uses a weird keyword syntax for which there is no first class support.

So even if we propose this, IMO we should still also propose to add a note to the function invocation syntax section, that a function may resolve to a JPA vendor defined funciton as well. This would be like a "last resort" to use a function at least in a "standard way". If the JPA vendor doesn't define the desired function, it's up to the user to making use of JPA vendor specific APIs for registering the function.