On Tue, Apr 24, 2018 at 5:43 PM Christian Beikov <christian.bei...@gmail.com> wrote:
> 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. > And not only that but some databases allow extensions to the SQL spec as to what can be extracted. So using an enum is nice, but limiting > 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. > I'm not sure what this means _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
