Hints to the driver that a request, an independent unit of work, is beginning on this connection. Each request is independent of all other requests with regard to state local to the connection either on the client or the server. Work done between beginRequest, endRequest pairs does not depend on any other work done on the connection either as part of another request or outside of any request. A request may include multiple transactions. There may be dependencies on committed database state as that is not local to the connection.
… is optional, vendor specific and should largely be transparent.
➠ Please explain the purpose of this feature.
It seems to be about something larger than transactions yet is not about two-phase commits. Is it related to sharding, the major new feature in JDBC 4.3?
- Is it some kind of scope that wraps around multiple transactions?
- What databases make use of this feature?
I am not asking about whether these databases have JDBC drivers updated yet for JDBC 4.3 yet. I am asking about the bigger picture, what is the meaning and purpose of a "request" in the context of a database connection across connections.
Oddly, the JDBC 4.3 specification makes only this one mention, with no explanation:
JDBC API changes
The following changes were made to existing JDBC interfaces..
Added the methods