Inserting long strings into CLOB column

[cfcoder2]

I have a chunk of text data that exceeds 4k bytes. I've created a table that
has a column defined to be a CLOB. I'm using Oracle 8i and trying to insert
records into this CLOB column. When I insert rows, a bunch go in but then I
get the error: [Macromedia][Oracle JDBC Driver]long (>4k) parameters are only
allowed in the values list of simple insert/update statements The error
occurred in ...(removed)/import_faqs.cfm: line 151 149 : '#SW#', 150 :
'#WAN#', 151 : <cfif FinalSol neq ''><cfqueryparam cfsqltype='CF_SQL_CLOB'
value='#FinalSol#'><cfelse>empty_clob()</cfif> 152 : ) 153 : </cfquery>
INSERT INTO faq (qid, question, created_date, modified_date, description,
hardware, keywords, os, software, webagent_note, solution) VALUES ( 'S10072',
'What can I do if my license file is not working (param 1) ',
TO_DATE('2001-08-31','YYYY-MM-DD'), TO_DATE('2004-04-08','YYYY-MM-DD'),
'Situation: My software will not run properly because of a license problem.
Discussion: The current software requires a license based on the volume serial
number of your primary (C:) hard disk drive. A Windows environment variable is
used to locate the file containing the license information.', '', '', 'Windows
NT 4.0,Windows 95,Windows 98,Windows 2000 Professional', 'ispLEVER Features
Licensing,Licensing,ispLEVER,software,downloads,se rvice pack,ispdesign,isplever
starter,update,lever,isplever-starter,starter,isplever
v3.1,ispDesignExpert,ispexpert,ispdesign,design expert,isp design
expert,designexpert,ispdesign expert,ispDesignEXPERT', '', (param 2) )
DATASOURCE dweb SQLSTATE HY004 What is a 'simple' insert? Why is it
choking?

[davidsharpe]

I know this comes a bit late but i found this posting and wished someone had
replied to it so here goes.

We were getting the error:

[Macromedia][Oracle JDBC Driver]long (>4k) parameters are only allowed in the
values list of simple insert/update statements

I had this problem doing updates and inserts with clobs using MX7 and Oracle
8.17 - turned out it was my understanding of what a simple insert/update
statement' was that was causing the issue.

We were using using table names which were set as variables elsewhere in the
app.
for example <cfset tablename = "Mydatasource.CONTENT a">

This meant the query was something like: UPDATE Mydatasource.content a SET
field1 = #form.value1# WHERE a.id = #form.id#

Simply changed it to:

<cfset tablename = "Mydatasource.CONTENT ">

Which produces:

'UPDATE Mydatasource.content SET field1 = #form.value1# WHERE id = #form.id#

And it worked

So removing the alias 'a' fixed the problem.

Hope this helps someone