We have migrated one of our datatypes from LONG to CLOB, but we're running into a major issue with selects, inserts and updates (that pretty much makes the CLOBs useless...)
The issue is that because of the manner Oracle has implemented CLOBs and the way in which Witango handles a CLOB, if there is more than about 4000 characters, we encounter a failure e.g., in some cases, (perhaps those right on the borderline) the insert/update occurs, but the data is truncated to 4000 chars. In other cases, nothing is inserted or the field is updated to null, depending on the action.
This is true in the 5.0, 5.5 Witango servers, while the J2EE server gave us the clue - it refuses to deal with an insert/update of more than 4000 characters, giving us a "literal string too large" error.
So far the only "work around" I can think of is to have TWO CLOB fields (summary and summary2), putting the first 3500 chars in summary and any remaining ones in summary2, but that is a pretty klutzy solution.
Our understanding is that this problem is solely limited to Oracle (heh heh, comments on how other DBs handle this won't help us...)
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
