Hi,

I looked through the FAQ and search around but could not find an answer to this question, which I'm sure must've come up before.

When generating the mapping file using middlegen all varchar2 fields appears with columnlength * 4? Number "length" is picked up correctly. I double checked using desc in sqlplus when connected to the source database. I'm using the ojdbc14.jar jdbc drivers for oracle 9.2.0

Any ideas?

Thank you,
Peter

A small example would be good just to illustrate.

Hi David,

I'm sorry, here's an example:

This is from the source database:

SQL> desc imihs_commitment_doc_t
Name Null? Type
----------------------------------------- -------- ----------------------------
FDOC_NBR NOT NULL VARCHAR2(36 CHAR)
FDOC_EXPLAIN_TXT VARCHAR2(1600 CHAR)
CATEGORY VARCHAR2(160 CHAR)
PRIMARY_RECIPIENT VARCHAR2(160 CHAR)
PRIMARY_DEPARTMENT VARCHAR2(160 CHAR)
SECONDARY_RECIPIENT VARCHAR2(160 CHAR)
SECONDARY_DEPARTMENT VARCHAR2(160 CHAR)
TOTAL_AMT NUMBER(19,2)

Middlegen generates the following:

<id
name="fdocNbr"
type="java.lang.String"
column="FDOC_NBR"
>
<generator class="assigned" />
</id>

<property
name="fdocExplainTxt"
type="java.lang.String"
column="FDOC_EXPLAIN_TXT"
length="4000"
/>
<property
name="category"
type="java.lang.String"
column="CATEGORY"
length="640"
/>
<property
name="primaryRecipient"
type="java.lang.String"
column="PRIMARY_RECIPIENT"
length="640"
/>
<property
name="primaryDepartment"
type="java.lang.String"
column="PRIMARY_DEPARTMENT"
length="640"
/>
<property
name="secondaryRecipient"
type="java.lang.String"
column="SECONDARY_RECIPIENT"
length="640"
/>
<property
name="secondaryDepartment"
type="java.lang.String"
column="SECONDARY_DEPARTMENT"
length="640"
/>
<property
name="totalAmt"
type="java.math.BigDecimal"
column="TOTAL_AMT"
length="19"
/>


The reason why I think might have something to do with the jdbc metadata is because my sql client (DbVisualizer) reports the same wrong values!

Thanks,
Peter

I would agree that this is most likely to be the JDBC driver as the length attribute is taken from the JDBC drivers meta data directly. Oracle has had a few bugs in their JDBC drivers from time to time. Try the latest or a some alternate JDBC driver release.