Two more points:

• Ideally the type of a parameter would depend on the parameter only, that is be independent of the result type.
  In cases where the result is based on a calculation it should be possible to pass in all kinds of types for the operands. For example passing 2.5d and 2f to a calculation expected to return Integer seems fine to me, and I would expect the result of (int) (2.5d * 2f) to be 5.
• Hibernate is usually really good at this, too! It only seems to fail when I use an entity field in the calculation (which I wish I didn’t have to but that’s another discussion)
  Consider the following almost-identical queries:

  // Let test.intField be initialized to 2, int
  session.createQuery("""
  			UPDATE TestEntity test
  			SET test.bigDecimalField = test.intField * ?1
  			""")
  			.setParameter(1, BigDecimal.valueOf(2.5d))
  			.executeUpdate();
  // Result: Parameter value [2.5] did not match expected type [BasicSqmPathSource(intField : Integer) ]
  
  // Let passing same value (2, int) as a query param instead of reading the entity field
  session.createQuery("""
  			UPDATE TestEntity test
  			SET test.bigDecimalField = ?1 * ?2
  			""")
  			.setParameter(1, 2)
  			.setParameter(2, BigDecimal.valueOf(2.5d))
  			.executeUpdate();
  // Result: Update successful, value of 5.00 confirmed in entity