If I remember correctly there are two other types that are missing a
set by name function in the standard API.
Also if the type contributor I proposed in PR #1499 is not going to
make it in, should I just close it and release it stand-alone?
I think there might be an optimization or two that I haven't pushed to it.
On 7 June 2017 at 12:25, Vlad Mihalcea <mihalcea.v...@gmail.com> wrote:
> Hi,
>
> While writing an example for a custom Hibernate Type which supports
> PostgreSQL arrays,
> I realized that the SqlTypeDescriptor only supports bind by name:
>
> @Override
> protected void doBind(CallableStatement st, X value, String name,
> WrapperOptions options)
> throws SQLException {
> }
>
> However, for the java.sql.Array, we only have a bind by index method in
> java.sql.Statement:
>
> void setArray (int parameterIndex, Array x) throws SQLException;
>
> I remember that 6.0 is going to bind by index, so maybe this issue is
> already taken care of in the new version.
> Should we provide some fix for 5.x as well?
>
> Vlad
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
