You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Addison (JIRA)" <ji...@apache.org> on 2018/05/03 14:36:00 UTC
[jira] [Updated] (GEODE-4833) JdbcWriter and JdbcAsyncWriter may
fail to write null fields to database
[ https://issues.apache.org/jira/browse/GEODE-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Addison updated GEODE-4833:
---------------------------
Fix Version/s: (was: 1.6.0)
1.7.0
> 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.7.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)