Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7EEDE17B4C for ; Fri, 27 Mar 2015 23:35:02 +0000 (UTC) Received: (qmail 44033 invoked by uid 500); 27 Mar 2015 23:34:53 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 43995 invoked by uid 500); 27 Mar 2015 23:34:53 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 43983 invoked by uid 99); 27 Mar 2015 23:34:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Mar 2015 23:34:52 +0000 Date: Fri, 27 Mar 2015 23:34:52 +0000 (UTC) From: "Daniel Barclay (Drill) (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DRILL-2613) Implement (higher-priority) ResultSet.getXxx(...) data conversions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DRILL-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384892#comment-14384892 ] Daniel Barclay (Drill) commented on DRILL-2613: ----------------------------------------------- Notes on requirements, possibilities, considerations, etc: - The JDBC specification (PDF file) does not seem to require any conversions. It does have a matrix (in 4.1) or table (in 4.2) about conversions, but it seems to specify _allowed_ conversions, not _required_ conversions. (Note that it has a column labeled "Java Object Type" with entries such as "getFloat" (a _method_ name), so ...) - Other JDBC drivers implement some conversions. It is not yet clear what is typical or is expected by tools calling JDBC. - Conversion from a narrower type (e.g., INTEGER/int) to a wider type (BIGINT/long) should work fine. - For conversion from a wider type to a narrower type, there is the question of what happens if the value of the wider type is not a value of the narrower type (doesn't fit in the narrower type). Should that dynamic case throw an exception? Should it ignore the overflow? Should it be a warning (returning a truncated value and adding a SQLWarning to the ResultSet's list of warnings)? Should conversion from a wide type to a narrower type not be supported? > Implement (higher-priority) ResultSet.getXxx(...) data conversions > ------------------------------------------------------------------ > > Key: DRILL-2613 > URL: https://issues.apache.org/jira/browse/DRILL-2613 > Project: Apache Drill > Issue Type: Bug > Reporter: Daniel Barclay (Drill) > -- This message was sent by Atlassian JIRA (v6.3.4#6332)