Oh, I forgot. Check out cfprocparam in the 4.5 documentation. That's supposed to do this more simplistically on your end. At 04:50 PM 7/5/00 -0700, you wrote: >Anyone know of any new workarounds for the 4000 character limit on >updates/inserts to an Oracle database, or a fix for the problem? This is >the one that returns an error of "string literal too long". I am on CF4.5, >Oracle8.0.5, NT4.0, native drivers. It works using a stored procedure, but >my code for the stored procedure below, which is as simple as I think I can >get it, is taking too long. If it fails on the insert and then does the >update, the normal scenario, I'm losing about 60-80ms, compared to the 10ms >it takes to select the same data out of the table through the native >drivers. > >Thanks for any insights . . . . >Dan > >** Oracle Stored Procedure ** >procedure update_state(p_cfid IN varchar2, p_state IN long) >as >begin > insert into app_state > (cfid, state, lastwritten) > values > (p_cfid, p_state, sysdate); >exception > when dup_val_on_index then > update app_state > set state = p_state, > lastwritten = sysdate > where cfid = p_cfid; >end; > >------------------------------------------------------------------------------ >Archives: http://www.mail-archive.com/[email protected]/ >To Unsubscribe visit >http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or >send a message to [EMAIL PROTECTED] with 'unsubscribe' in >the body. ------------------------------------------------------------------------------ Archives: http://www.mail-archive.com/[email protected]/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
