NoSQL databases need to be allowed to raise errors for function that the database type is not capable of

[njr-11]

We need to update the specification (section 5.4.5?) to permit NoSQL databases to raise UnsupportedOperationException for operations that the category of NoSQL database (key-value, document, ...) is not capable of.

Refer to the table from Otavio, https://github.com/jakartaee/data/pull/771/files#r1649951754 which has a lot of information, and needs further clarification beyond that (for the ones that are maybe/some).

The TCK also needs to trap UnsupportedOperationException and allow if not required for that database type.

Here is a checklist where we can add separate PRs for the work:

• TCK cannot require GT, GTE, LT, LTE for Key-Value databases #779
• TCK cannot require Contains, EndsWith, IgnoreCase, Like, Null, StartsWith for Document and Graph, TCK cannot require Between, True, False for Key-Value #783
• limitations on sorting and In, Or, And keywords #794
• TCK cannot require totalElements and totalPages of some NoSQL databases - Otavio needs to clarify which types of NoSQL databases can support counts and which cannot.
• TCK cannot expect NoSQL to be capable of arithmetic in updates #806
• Document databases might not be capable of parentheses
• Per Disable Return of Affected Records Count for Update and Delete Operations in NoSQL Databases #828 document that UnsupportedOperationException can be raised on Delete methods that return an update count when a non-relational database relies on eventual consistency and is incapable of knowing the count of deleted entities.

After completing the above, add documentation of the above in the next release.

[gavinking]

Assign this to me if you like (and assuming you're not in a super hurry to get it done right away).

[njr-11]

Assign this to me if you like (and assuming you're not in a super hurry to get it done right away).

Definitely not in a hurry here. Specification updates should be delayed until 1.1.