[
https://issues.apache.org/jira/browse/GEODE-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680403#comment-16680403
]
Alexander Murmann commented on GEODE-4833:
------------------------------------------
[~agingade] [~dschneider] The associated PR was merged a long time ago, but we
seem to be pushing the release version up. Should this be indicated as shipping
with 1.8.0 or is this not fixed? If it's not fixed, I'd suggest removing the
fix version, since it just causes confusion every time we are trying to release.
> JdbcWriter and JdbcAsyncWriter may fail to write null fields to database
> ------------------------------------------------------------------------
>
> Key: GEODE-4833
> URL: https://issues.apache.org/jira/browse/GEODE-4833
> Project: Geode
> Issue Type: Bug
> Components: extensions, regions
> Affects Versions: 1.4.0
> Reporter: Darrel Schneider
> Assignee: Anilkumar Gingade
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Both JdbcWriter and JdbcAsyncWriter end up calling the JDBC method
> PreparedStatement.setObject with a value of "null" if the pdx field contains
> "null".
> This will work with jdbc drivers that support sending "non-typed Null" to the
> backend database.
> But some drivers do not support this and these puts will fail with a
> SQLException.
> For portability the jdbc connector should be changed to not pass "null" to
> setObject without a type.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
