On an Oracle DB, if a CLOB contains any non-Ascii
data, it's munged on retrieval. (In TJDO, CLOBs are
used to persist very very large strings; max length >
either 2k or 4k, I think.) Ascii strings stored in
CLOBs are not affected.
The problem is obvious, in the
com.triactive.tjdo.store.OracleCobMapping.getString()
method.
A *preliminary* patch file for TJDO 2.0 and for TJDO
2.1 will be attached; we're still evaluating this fix.
The changes are actually the same, just to different lines.
Mike Martin
None
None
Public
|
Date: 2005-03-03 17:09 Logged In: YES |
|
Date: 2005-01-23 18:23 Logged In: YES |
|
Date: 2005-01-09 23:12 Logged In: YES |
| Filename | Description | Download |
|---|---|---|
| OracleClobMapping.patch.2.0 | Patch for TJDO 2.0 | Download |
| OracleClobMapping.patch.2.1 | OracleClobMapping.patch.2.1 | Download |
| Field | Old Value | Date | By |
|---|---|---|---|
| status_id | Open | 2005-01-23 18:23 | jackknifebarber |
| resolution_id | None | 2005-01-23 18:23 | jackknifebarber |
| assigned_to | nobody | 2005-01-23 18:23 | jackknifebarber |
| close_date | - | 2005-01-23 18:23 | jackknifebarber |
| File Added | 115181: OracleClobMapping.patch.2.1 | 2005-01-09 23:12 | studerby |
| File Added | 115180: OracleClobMapping.patch.2.0 | 2005-01-09 23:02 | studerby |