[
https://issues.apache.org/jira/browse/TAJO-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008134#comment-14008134
]
ASF GitHub Bot commented on TAJO-842:
-------------------------------------
GitHub user babokim opened a pull request:
https://github.com/apache/tajo/pull/18
TAJO-842: NULL handling in JDBC.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/babokim/tajo TAJO-842
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/18.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #18
----
commit 8731ebc2f2a7dd57b41b3dc9a7c296718f49cc47
Author: 김형준 <[email protected]>
Date: 2014-05-24T14:02:43Z
TAJO-842: NULL handling in JDBC.
----
> NULL handling in JDBC.
> ----------------------
>
> Key: TAJO-842
> URL: https://issues.apache.org/jira/browse/TAJO-842
> Project: Tajo
> Issue Type: Improvement
> Reporter: Hyoungjun Kim
> Assignee: Hyoungjun Kim
>
> Currently JDBC doesn't handle NULL value, only wasnull() is provided. JDBC
> handles NULL data like the following rule.
> - Text type: return java null.
> - Int, Float type: return 0
> - Date/Time type: return null.
> - Boolean: return false
> - getObject(): return java null
--
This message was sent by Atlassian JIRA
(v6.2#6252)
