ora 01704 string literal long

Oracle ORA-01704: string literal too long problem analysis today when using SQL in oracle to directly insert update a table, the error of ORA-01704: string literal too long occurs, our SQL is [SQL] update mall_config a set. category_info = '|

When using SQL to insert update a table directly in Oracle today, the error of ORA-01704: string literal too long occurs. Our SQL is UpdateMall_configSetA. category_info ='| Standard Among them, the category_info field is of the clob type, and the

Analysis: The large text in Oracel cannot be inserted directly because Oracle will automatically convert CLOB to string, when the text byte exceeds 4000 bytes, the hint character is too long.Note: GBK encoding: A kanji account of two bytes . UTF-16

Today, when using SQL in oracle direct insertupdate for a table, the error of ORA-01704: stringliteraltoolong occurs, and our SQL is updatemall_confi The error of ORA-01704: string literal too long occurs when SQL is used to insert update a table

The analysis of CLOB type processing in the original Broken Sword ice-oraclePrevious analysis: ORA-01461: Can only bind a long value to insert a long columnMost recently, for the Clob field, when inserting data, the number of bytes in the character (

Summary The most recent use of the NHibernate mapping type for the Clob field when inserting data is when the number of bytes (a half-width character, one byte, one full-width character, two bytes) between 2000-4000 times is incorrect (ORA-01461:

Recently when writing SQL statements, encountered two problems: 1) ORA-01795: maximumnumberofexpressionsinalistis1000 cause: Write such SQL statement: Recently I encountered two problems when writing SQL statements: 1) ORA-01795: maximum number of

Some problems occurred when using ORACLE in the actual project. The problem is avoided through the work und. I wrote this article to make it easy to use! 1. ORA-01403: no data found-NO DATA FOUND A. Add an exception to handle the exception. Code

When I was writing SQL statements recently, I encountered two problems: 1) ORA-01795: maximum number of expressions in a list is 1000 Cause: the following SQL statement is written: SELECT PALLET_ID, BOX_ID, STATUS FROM SD_CURRENT_BOX WHERE

System Environment xp+.net2.0+oracle9i Table structure (because it is a test, the table structure casually built a sheet) XX Field name Type Id VARCHAR2 (70) TEST Clob Test Mode 1: Spell the CLOB value directly in the SQL statement. Code: