The givenSQL statement must have exactly the number of JDBC? parameters that Hibernate expects, that is, one for each column mapped by the entity, in the exact order Hibernate expects. In particular, theprimary key columns must come last.

If a column shouldnot be written as part of the insert statement, and has no corresponding JDBC parameter in the custom SQL, it must be mapped usinginsertable=false.

A custom SQL insert statement might assign a value to a mapped column as it is written. In this case, the corresponding property of the entity remains unassigned after the insert is executed unless@Generated is specified, forcing Hibernate to reread the state of the entity after each insert.

Similarly, a custom insert statement might transform a mapped column value as it is written. In this case, the state of the entity held in memory loses synchronization with the database after the insert is executed unless@Generated(writable=true) is specified, again forcing Hibernate to reread the state of the entity after each insert.

If an entity hassecondary tables, it may have a@SQLInsert annotation for each secondary table. Thetable() member must specify the name of the secondary table.