[ http://issues.apache.org/jira/browse/DERBY-102?page=comments#action_12319065 ]
Satheesh Bandaram commented on DERBY-102: ----------------------------------------- Clobs can be as large as upto 2GB. So, even if this limit is relaxed, passing a large clob constant could still hit the maximum size of the query limit. I am not exactly sure if Derby has a limit on maximum size of a query, but it may be present. It is also inefficient to insert large data using character constants. Are there any problems using PreparedStatements and parameters? If it is required to avoid PreparedStatements, it may be possible to use functions to import clob data at runtime. Clob data will have to be placed in files and a file name could be passed as an argument to this import function. > can not insert more than 32270 charakters in long varchar, clob > --------------------------------------------------------------- > > Key: DERBY-102 > URL: http://issues.apache.org/jira/browse/DERBY-102 > Project: Derby > Type: Bug > Components: Documentation > Versions: 10.0.2.1 > Environment: Windows XP/2000 > Reporter: rainer garbotz > Priority: Critical > Fix For: 10.1.1.0 > > I have created an table with > create table egal ( > text long varchar > ); > Now I try to insert an 38000 charakters long String. > insert into egal values (' > ...... > '); > But there are following error message: > ERROR 54002: A string constant starting with '' > ddddddddddddddddddddddddddddddddddddddddddddddddddddddddd&' is too long. > I tryed the same with CLOB, but the same error occures. > The "Reference Manual" says to LONG VARCHAR: > "The LONG VARCHAR type allows storage of character strings of unlimited > length" > Have I missunderstood this, or is this a BUG. > Thanks > Rainer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
