[
https://issues.apache.org/jira/browse/GEODE-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16405328#comment-16405328
]
ASF subversion and git services commented on GEODE-4833:
--------------------------------------------------------
Commit b4ad610f1bd20b7b87e9679b4637893e2bf3c5b8 in geode's branch
refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b4ad610 ]
GEODE-4833: JdbcWriter and JdbcAsyncWriter may fail to write null fields to
database (#1636)
Null values are now supported. Meta-data read from the database is now used to
determine the
column type and used to call setNull.
* Renamed TableKeyColumnManager to TableMetaDataManager
* registerPdxMetaData will now throw an exception if the instance is not
serialized with PDX
> 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: Darrel Schneider
> Priority: Major
> Labels: pull-request-available
> 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)
