Preface: if you are using stored procedure or prompt: string literal too long, use the following method
The core idea is string splicing
part1:
DECLARE
field1_clob clob := 'first half part';
BEGIN
update T_protocol set protocol_content = field1_clob where protocol_id = '111';
END;
commit;
part2:
DECLARE
field1_clob clob := 'second half part';
BEGIN
update T_protocol set protocol_content = protocol_content||field1_clob where protocol_id = '111';
END;
commit;
See section 38142142nd;: https://blog.csdn.net/weixin_40241267/article/details/78923706
Similar Posts:
- Solution to the error of ora-06550 pls-00103 when Django connects Oracle to run PLSQL statement
- 「ImportError: libcublas.so.10.0: cannot open shared object file: No such file or directory」
- bash :startx command not found
- Java.net.noroutetohostexception: cannot assign requested address
- SVN commit Issue POST of ‘***/!svn/me’ 403 forbidden
- [Solved] Makefile xxx recipe for target xxx failed
- Tomcat7 java.lang.ClassNotFoundException: org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory
- HTTP protocol error: com.sun.net.ssl.internal www.protocol.https.HttpsURLConnectionOldImpl resolvent
- Error:Connection activation failed: No suitable device found for this connection
- Python — the copied virtual environment PIP command failed to run. Fatal error in launcher: unable to create process using