Yes there is a problem but I like to say *BUT* here :
Indeed the testcase truncates the LONG actually the testcase uses ORACLE LONG data type and not VARCHAR2 > 254 or CLOB...Now if you use those you would have no such problem (I tested it), not to say (ME) you should not use them but from ORACLE and MS LONG DATATYPE are deprecated since 9i...see
http://msdn.microsoft.com/en-us/library ... 10%29.aspx
In any case this used to work in 6.0 SP3 or 5.2 SP3, broken in 6.0 SP3 EMP5361 a 5.2 SP4 and interestingly enough the SAME PROBLEM happens with LONG RAW as I entered recently an issue for thatStarting with the Oracle database 9i release, the LONG data type is deprecated. Oracle recommends using the LOB data types instead. Hence, when performing operations on the Oracle database using the Oracle Database adapter, we recommend using Oracle database artifacts that operate on LOB data types and not the LONG data type.
ORACLE LONG RAW DATA truncation
You can test if you want with this : https://support.guptatechnologies.com/supportforum/viewtopic.php?f=32&t=1735
It fails with LONG RAW but is OK with BLOB.
So it is the SAME issue and will add this TESTCASE (FOR TEXT) to this BUG and remove the "RAW" in description.
Basically we see problems with oracle LONG; but as far as I can see it is all OK with TEXT varchar2>254/CLOB and BINARY BLOB data types including concatenation now...
So I would recommend to use them and not the deprecated data types...soon or later will have problem if continue using them also I would believe from what I recall that you might see some performance issue with them...I'm not 100% sure but recall issues along those lines possibly depending the ORACLE client used..recall we certified 9i R2 but removed it...(as no longer supported by ORACLE) yet you still can connect with WIN32 using 9i but no one should do that...