Do we want to support a boolean return value for @Query("UPDATE... ?

[njr-11]

Currently the Query Javadoc requires void, int, or long.

A TCK test was testing a boolean return type, but is being changed in #924 as the resolution to challenge #923 because the Javadoc does not currently permit boolean.

boolean would be trivial to implement, with true corresponding to a numeric result > 0, and false corresponding to a numeric result of 0.

boolean could be convenient when writing an DELETE or UPDATE statement (such as the one in the TCK) where there can be at most 1 matching entity, often due to querying based on the Id.

I'm fine with adding boolean, but the spec is also okay without it.

[gavinking]

I implemented it. (I guess because the TCK wanted me to, I don't actually recall.) But I don't see it as something that we need to require.

[otaviojava]

In my case, I did this mainly because the TCK, once the majority of the NoSQL databases, works with eventual persistence, thus as fewer options to update are better.