[hibernate-dev] 6.0 - procedure/function calls via NativeQuery
mihalcea.vlad at gmail.com
Thu Jul 27 04:54:55 EDT 2017
If we make this change, we need to make sure the StoredProcedureQuery works
properly for functions too:
Currently, it only supports stored procedures and not database functions.
However, users can also use session.doWork instead so there is a workaround
On Thu, Jul 27, 2017 at 11:37 AM, Arnold Gálovics <galovicsarnold at gmail.com>
> @Vlad: if they eventually have to adjust their code, why is it so hard to
> use the proper API for calling stored procedures?
> I'm supporting Steve's idea to remove this complexity and force the users
> to use the proper API. I think for 6.0 this change can be acceptable and
> should be mentioned in the migration guide.
> Best Regards,
> On Thu, Jul 27, 2017 at 7:25 AM, Vlad Mihalcea <mihalcea.vlad at gmail.com>
>> I run a quick Google search for "Hibernate NnativeQuery stored procedure"
>> and found these links:
>> I guess people used to do this. We could use some QueryHint which needs to
>> be supplied when users want to execute a SP via NativeQuery.
>> I think it's less painful to have this option instead of disallowing it
>> On Thu, Jul 27, 2017 at 1:08 AM, Steve Ebersole <steve at hibernate.org>
>> > Another unnecessary complexity I'd like discuss removing is the ability
>> > execute procedure/function calls via NativeQuery. The complexity is a
>> > bunch of String parsing and token interpretation we need to do in order
>> > discovery this intention. Given that both JPA and Hibernate define
>> > specific APIs for executing procedure/function calls this seems like an
>> > unnecessary complexity and overhead.
>> > Objections? Thoughts?
>> > _______________________________________________
>> > hibernate-dev mailing list
>> > hibernate-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
More information about the hibernate-dev