On 19 Jan 2013, at 3:46 PM, Steve Ebersole wrote:
> The trouble is that hints are valid on StoredProcedureQuery whether named or
> not. If we go the route of using hints for annotations, doesn't it make
> sense to be consistent and use that when building a StoredProcedureQuery too?
For me a
The trouble is that hints are valid on StoredProcedureQuery whether
named or not. If we go the route of using hints for annotations,
doesn't it make sense to be consistent and use that when building a
StoredProcedureQuery too?
On 09/19/2013 03:54 AM, Hardy Ferentschik wrote:
> Here are my 0.02
Here are my 0.02$ which need to be taken with a grain of salt since I am not so
familiar with the
procedure call stuff.
On 17 Jan 2013, at 6:15 PM, Steve Ebersole wrote:
> In my opinion, ideally the JPA spec would have defined a separate method
> to register a "function return". Luckily since
RE: https://hibernate.atlassian.net/browse/HHH-8445
I'd like to get opinions on this. Essentially the JPA spec
(StoredProcedureQuery) is silent on how/if calling database functions
through this API is supposed to be supported. I asked for clarification
of this from the rest of the EG, but got
