Bump it up to a meg. Troy
-----Original Message----- From: Dale Graham [mailto:[EMAIL PROTECTED] Sent: Thursday, July 08, 2004 8:33 AM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: CLOB (in Oracle) problem Thank you, we'll try it. How large do you suggest we make this? (Largest size we enter is 7900 characters.) On Jul 8, 2004, at 9:55 AM, Troy Sosamon wrote: > > There is a Tango setting called ItemBufferSize. > You can change it by editing the Tango.ini file (I think that's the > name) or > through the Tango Configuration Console under Data Sources. > This setting controls the size of the largest piece of data you can > send to > the server. I always need to bump it up on servers where I store > scanned > documents or pictures in the database as BLOBs. > > Troy > > -----Original Message----- > From: Dale Graham [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 08, 2004 6:29 AM > To: [EMAIL PROTECTED] > Subject: Witango-Talk: CLOB (in Oracle) problem > > Hopefully one of you Oracle guys will have a solution and/or > workaround... > > 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 > > _______________________________________________________________________ > _ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
