How about this rule then?
castTarget
// should allow either
// - named cast (IDENTIFIER)
// - JavaTypeDescriptorRegistry (imported) key
// - java.sql.Types field NAME (coded cast synonym - field's value)
// - "pass through"
// - coded cast (INTEGER_LITERAL)
// - SqlTypeDescriptorRegistry key
: IDE
On 30 May 2017 at 13:02, Steve Ebersole wrote:
> For whatever reason JPA and a few of the databases do not categorize
> coalesce and nullif as functions - hence the "not technically a function"
> part.
>
> However in Hibernate I have defined them as functions for the sake of users
> being able to
For whatever reason JPA and a few of the databases do not categorize
coalesce and nullif as functions - hence the "not technically a function"
part.
However in Hibernate I have defined them as functions for the sake of users
being able to plug in custom function templates.
On Tue, May 30, 2017 at
Hi Steve,
just a curiosity; for `coalesce` and `nullif` you stated "not
technically a function, but supported as such to allow overriding".
What does it mean?
Thanks!
Sanne
On 29 May 2017 at 22:29, Steve Ebersole wrote:
> Hibernate has always defined a set of functions that should always be
> a
