I have heard no feedback, especially in regards to my last comment on the
Jira. So at this point I plan on simply not supporting that atm from the
JPA APIs.
Longer term I think the correct solution is to expose the underlying
Hibernate parameter object and users can directly set it. Handling this
via hints just feels completely icky to me.
On Tue, Jan 5, 2016 at 12:11 PM Steve Ebersole <steve(a)hibernate.org> wrote:
HHH-9548[1] presents an interesting conundrum in terms of how to
handle
null parameter values in regards to stored procedures and specifically in
terms of any argument defaults that might be defined on the database. At
the moment our support decides to not pass along the null in the desire to
not "over power" any defined argument defaults - if we pass the NULL, the
database would use that rather than the defined argument default.
Essentially it is one of those 50/50 calls. I started a discussion on the
JIRA, but please add your thoughts...
[1]
https://hibernate.atlassian.net/browse/HHH-9548