The in length of an Oracle SQL statement cannot exceed 1000

1. the maximum number of lists IN the IN clause is 1000. If this number is exceeded, an error is returned. You can use a temporary table to solve this problem;

2. * The character length of the create trigger statement text cannot exceed 32 KB (the LONG and long raw types cannot be used in the TRIGGER. You can refer to the column values of the LOB type columns in the TRIGGER, but cannot pass: NEW modifies data in the LOB column.) By the way, the PARENT keyword in the trigger is only valid in the nested table trigger,

3. * Before 11G, DBMS_ SQL cannot exceed 32 kb for the input SQL, because the input parameter can only be of the VARCHAR2 type. After 11G, CLOB can be used as the input parameter. Therefore, this restriction is canceled.

3. * The maximum package, process, function, and trigger size of a PL/SQL statement is 64 kB in UNIX, while 32 kb in WINDOWS, see the test below)

4. * How long can an SQL statement be? (According to netizens) the Oracle document is 64 KB. In fact, some tools may have lower limits than this value. However, it may take a long time to test it, even more than 1 MB (I tested K ). The specific length is 10 Gb, which is only related to many environments: database configuration, disk space, and memory size...

5. in PL/SQL, the length of expressions/SQL itself can reach a relatively long length (50 K), such as: v_str: =: new. f1 |: ndw. f2... ; Select: new. f1 |: new. f2... Into v_str from dual; in addition, if you write: v_str: = 'A' | 'B' |... The allowed expression length is greatly reduced. If the expression/SQL is too long and exceeds the maximum program length allowed by an ORACLE package/procedure, a pls-123: program too large error is reported during compilation, this is caused by restrictions on the pl/SQL Compiler itself, that is, the length of expressions/SQL is limited by the maximum size of packages/processes in PL/SQL.