The runtime handle the provider is resolved from.
The connection string.
The runtime handle.
The connection string.
The connection details, broken out.
The runtime handle.
The credentials.
Reports whether the capability is actually usable on this runtime.
The runtime handle.
true when calls will reach a real backing resource.
A capability backed by an optional resource answers false when that
resource was never provisioned. Implementations must document what each
method does in that state — degrade or throw — and must not vary it, since
a caller choosing between two implementations is relying on the answer
meaning the same thing in both.
Supplies connection details for an external SQL database.
Remarks
Deliberately not a query interface — it hands over credentials and stops there, leaving the driver to the caller. That separation is what makes the capability usable with whichever client the database needs, rather than committing the whole application to one.
Treat everything returned as short-lived: an implementation that pools connections may mint credentials per instance, so caching them beyond the current one is a bug that only appears under load.
Author
Bayu Dwiyan Satria
Version
1.0.0
Since
1.0.0