Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <25454187.113081283331233058.JavaMail.jira@thor>
Date: Wed, 1 Sep 2010 04:53:53 -0400 (EDT)
From: "Milosz Tylenda (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Commented: (OPENJPA-1779) Unknown column type returned for
 Oracle XMLType columns
In-Reply-To: <20009492.104011283294272929.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/OPENJPA-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904974#action_12904974 ] 

Milosz Tylenda commented on OPENJPA-1779:
-----------------------------------------

Mike, maybe it helps that in trunk Column.java tries to adapt to the magic 2007 number.

It looks like it is time to convert 2007 into a constant in OracleDicitonary or elsewhere.


> Unknown column type returned for Oracle XMLType columns
> -------------------------------------------------------
>
>                 Key: OPENJPA-1779
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1779
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.2.2
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>            Priority: Minor
>         Attachments: OPENJPA-1779-1.2.x.diff.txt
>
>
> I've only seen this as an issue when using Oracle's XMLType and using openjpa.jdbc.SchemaFactory=native to build mapping information from the database. There may be other ways this problem can be exposed.
> Recent versions of the JDBC driver for Oracle return 2007 as the DATA_TYPE for XMLType column (observed on 11.2.0.1.0). Earlier versions (10.2.0.3.0) returned java.sql.Types.OTHER. What's odd is that I don't see 2007 as a defined constant  for java.sql.Types - as a result OpenJPA throws an exception citing an unknown column type. It's not clear to me whether this is a bug in the JDBC driver or something we need to adapt to, or whether 2007 was just a holding place for Types.SQLXML (which is set to 2009). 
> As a workaround we can treat 2007 as Types.OTHER for Oracle (at least for OpenJPA 1.2.x).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.