HHH-9548[1] handles the question of what to do with null/unset parameter values in regards to calls to stored-procedures via JPA's StoredProcedureQuery contract. Do we just want to live with the overhead that comes from my last comment[2]? Another option I see would be an extension to javax.persistence.Parameter to return from the StoredProcedureQuery-defined access to parameter objects. Any other thoughts? [1] https://hibernate.atlassian.net/browse/HHH-9548 [2] https://hibernate.atlassian.net/browse/HHH-9548?focusedCommentId=74853&am... _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Right On Mon, Jan 25, 2016 at 12:41 PM andrea boriero <dreborier(a)gmail.com&gt; wrote: > do you mean to extend javax.persistence.Parameter with a sort > of enablePassingNulls() method? > > On 25 January 2016 at 17:56, Steve Ebersole <steve(a)hibernate.org&gt; wrote: > >> HHH-9548[1] handles the question of what to do with null/unset parameter >> values in regards to calls to stored-procedures via >> JPA's StoredProcedureQuery contract. >> >> Do we just want to live with the overhead that comes from my last >> comment[2]? Another option I see would be an extension >> to javax.persistence.Parameter to return from the >> StoredProcedureQuery-defined access to parameter objects. >> >> Any other thoughts? >> >> [1] https://hibernate.atlassian.net/browse/HHH-9548 >> [2] >> >> https://hibernate.atlassian.net/browse/HHH-9548?focusedCommentId=74853&am... >> > _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > >