ORA-24816: provides a scalable non-LONG Binding data solution after the actual LONG or LOB Column

ORA-24816: when the actual LONG or LOB column is followed by an extended non-LONG Binding data solution to add an announcement, an error is reported when the content is entered too: ORA-24816: after the actual LONG or LOB columns, the extended non-LONG Binding data solution is provided: after the actual LONG or LOB columns, the extended non-LONG Binding data error is provided, this error occurs because fields with the LONG field type in the database are placed before other fields during parameter binding. You only need to bind the fields with the LONG type to the final setting. Insert into ZGECM. ZHBGPT_GGXX (BT, BZ, FBRBH, FBRXM, FBSJ, FBZT, FJDZ, FJMC, NR, SFZD, SXRQ, YDFW, YDFWQD, YXRQ, zqsj, ID) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) Oh, is the content field to be put behind? Well, modify the program and modify the database. 1. modify the program: @ Entity @ Table (name = "ZHBGPT_GGXX", schema = "ZGECM") public class GgxxEntity implements Serializable {// Fields private int id; private String bt; private String sxrq; private String yxrq; private String ydfw; private String ydfwqd; private String fbrxm; private String fbrbh; private String fbsj; private String bz; private String fbzt; private String sfzd; private String zqsj; private String Fjmc; private String fjdz; private String zzz_nr; 2. modify the field corresponding to the database. 3. restart the service. OK. the insert statement has changed: insert into ZGECM. values (BT, BZ, FBRBH, FBRXM, FBSJ, FBZT, FJDZ, FJMC, SFZD, SXRQ, YDFW, YDFWQD, YXRQ, zqsj, ZZZ_NR, ID) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)