ORA-24816: provides extended non-LONG Binding data after the actual LONG or LOB Column

When an announcement is added, an error is reported when the content is entered: ORA-24816: provides extended non-LONG Binding data after the actual LONG or LOB Column

When an announcement is added, an error is reported when the content is entered: ORA-24816: provides extended non-LONG Binding data after the actual LONG or LOB Column

When an announcement is added, an error is reported when the content is entered: ORA-24816: provides extended non-LONG Binding data after the actual LONG or LOB Column

Solution: an extended non-LONG Binding data error is provided after the actual LONG or LOB column ,, 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 fields 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 (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)