You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
If you have multiple bind parameters for a @SqlBatch method, and one of the non-iterable parameter is NULL, the following error is thrown:
java.lang.NullPointerException
at org.jdbi.v3.core.internal.IterableLike.isIterable(IterableLike.java:48)
at org.jdbi.v3.sqlobject.statement.internal.SqlBatchHandler.zipArgs(SqlBatchHandler.java:269)
at org.jdbi.v3.sqlobject.statement.internal.SqlBatchHandler.invoke(SqlBatchHandler.java:174)
at org.jdbi.v3.sqlobject.internal.SqlObjectInitData$1.lambda$invoke$0(SqlObjectInitData.java:125)
at org.jdbi.v3.sqlobject.internal.SqlObjectInitData$1$$Lambda$614/447234532.call(Unknown Source)
at org.jdbi.v3.core.internal.Invocations.invokeWith(Invocations.java:44)
at org.jdbi.v3.core.internal.Invocations.invokeWith(Invocations.java:26)
at org.jdbi.v3.core.LazyHandleSupplier.lambda$invokeInContext$1(LazyHandleSupplier.java:77)
at org.jdbi.v3.core.LazyHandleSupplier$$Lambda$615/1028348585.call(Unknown Source)
at org.jdbi.v3.core.internal.Invocations.invokeWith(Invocations.java:44)
at org.jdbi.v3.core.internal.Invocations.invokeWith(Invocations.java:26)
at org.jdbi.v3.core.LazyHandleSupplier.invokeInContext(LazyHandleSupplier.java:76)
at org.jdbi.v3.sqlobject.internal.SqlObjectInitData$1.call(SqlObjectInitData.java:131)
at org.jdbi.v3.sqlobject.internal.SqlObjectInitData$1.invoke(SqlObjectInitData.java:125)
at org.jdbi.v3.sqlobject.SqlObjectFactory.lambda$attach$2(SqlObjectFactory.java:110)
Environment
Description:
If you have multiple bind parameters for a @SqlBatch method, and one of the non-iterable parameter is NULL, the following error is thrown:
Example,
durationMins
is null :This can probably be handled with a null check for the
IterableLike.isIterable()
method call:The
maybeIterable.getClass().isArray()
line is the one that's throwing NPE.The text was updated successfully, but these errors were encountered: