[jira] [Assigned] (GEODE-4833) JdbcWriter and JdbcAsyncWriter may fail to write null fields to database

2018-12-12 Thread Darrel Schneider (JIRA)


 [ 
https://issues.apache.org/jira/browse/GEODE-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darrel Schneider reassigned GEODE-4833:
---

Assignee: Darrel Schneider  (was: Anilkumar Gingade)

> 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
> Fix For: 1.9.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)


[jira] [Assigned] (GEODE-4833) JdbcWriter and JdbcAsyncWriter may fail to write null fields to database

2018-04-03 Thread Darrel Schneider (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darrel Schneider reassigned GEODE-4833:
---

Assignee: Nick Reich  (was: Darrel Schneider)

> 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: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.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)


[jira] [Assigned] (GEODE-4833) JdbcWriter and JdbcAsyncWriter may fail to write null fields to database

2018-03-13 Thread Darrel Schneider (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darrel Schneider reassigned GEODE-4833:
---

Assignee: Darrel Schneider

> 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
>
> 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)