Why does Hibernate only cache MULTIPLE prepared statements for queries, and not for updates/inserts?

I can see this would not work in every situation, but in some it would be most handy. Is this a feature you would like implemented?

No idea why, but I can suggest why not. Prepared statements are reasonably lightweight and don't take long to construct. Inserts and updates are simple operations, referring to columns in a single table. There isn't much advantage to caching the statements on the java side. And the database caches execution plans on the server side, so you get that performance benefit whether you use an old statement object, or a new one.

Query statements, however, can be very complex, referring to many tables, inclyuding subselects, and thus can involve some overhead at creation time. So hibernate can cache them, to avoid creating them more than once.

OK, that makes sense.

Caching multiple statements for insert/updates would allow you to take advantage of jdbc driver level batching. The way Hibernate deals with the prepared statements now prevents the drivers from doing this.

I'd like to know if it's something the team would actually be interested in adding to the project before I go off and spend the time to implement it.