You are viewing a plain text version of this content. The canonical link for it is here.

Posted to ddlutils-user@db.apache.org by Jun Li <al...@gmail.com> on 2006/04/28 05:26:03 UTC

Wrong type mapping on Oracle.

JDBC type LONGVARCHAR or OTHER could be varchar2 or nvarchar2 on Oracle 9i,
but it mapped into CLOB or BLOB.

--
--------------
Cheers,
Jun

Re: Wrong type mapping on Oracle.

Posted by Thomas Dudziak <to...@gmail.com>.

On 4/28/06, Jun Li <al...@gmail.com> wrote:

> JDBC type LONGVARCHAR or OTHER could be varchar2 or nvarchar2 on Oracle 9i,
> but it mapped into CLOB or BLOB.

No, they can't. nvarchar2 has a limit of 4000 bytes in Oracle 8i, and
in 9/10 the limit should be around the same number. LONGVARCHAR
however can - per JDBC doc
(http://java.sun.com/j2se/1.4.2/docs/guide/jdbc/getstart/mapping.html#996857)
- have lengths of 1G or more.
Similarily, OTHER is not constrained by JDBC and thus can only be
safely be mapped to a large binary type.

Tom