I had a developer came to me saying that we still had a problem with CLOB columns in production release of v8 (I had reported a corruption issue in one of the beta versions which has been fixed). He was having his data truncated.
After some investigation, I identified that PL/SQL Developer would not save more than 4000 characters in the column. That sounded fishy, so I did a describe on the table (which I should have done in the first place
) and determined that the column was not a CLOB, it was a VARCHAR2(4000). So, having the data truncated is to be expected.
It appears that PL/SQL Developer is doing one of two things. It is either not displaying the ORA-12899 error that Oracle returns when it truncates data, or it is doing the truncation itself before doing the insert/update. Either way, I would request that PL/SQL Developer be modified to notify the user if data truncation occurs.
Thanks, Maury
After some investigation, I identified that PL/SQL Developer would not save more than 4000 characters in the column. That sounded fishy, so I did a describe on the table (which I should have done in the first place

It appears that PL/SQL Developer is doing one of two things. It is either not displaying the ORA-12899 error that Oracle returns when it truncates data, or it is doing the truncation itself before doing the insert/update. Either way, I would request that PL/SQL Developer be modified to notify the user if data truncation occurs.
Thanks, Maury