Hey,
@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,
Arnold
On Thu, Jul 27, 2017 at 7:25 AM, Vlad Mihalcea <mihalcea.vlad(a)gmail.com>
wrote:
I run a quick Google search for "Hibernate NnativeQuery stored
procedure"
and found these links:
http://www.baeldung.com/stored-procedures-with-hibernate-tutorial
https://www.mkyong.com/hibernate/how-to-call-store-procedure-in-hibernate/
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
completely.
Vlad
On Thu, Jul 27, 2017 at 1:08 AM, Steve Ebersole <steve(a)hibernate.org>
wrote:
> Another unnecessary complexity I'd like discuss removing is the ability
to
> execute procedure/function calls via NativeQuery. The complexity is a
> bunch of String parsing and token interpretation we need to do in order
to
> 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(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev