Remote / foldkit-remote-drizzle
When the database fails
A caller reads nothing of the database. A statement the driver fails, a body
that cannot be compiled, a binding with no column for what a write names and
every other failure on the adapter's side fails its Source with a
RemoteServerError, which RemoteServer answers as Internal error with an
incident and reports as a ServerDefect under that id (see
When the server fails).
The table, the constraint and the SQL are in that report and in
StatementFailed, and in no answer.
The adapter tells a caller only about the request the caller itself sent, with
RemoteServer.tell. These arrive as written, with no incident:
| What the caller sent | What it reads |
|---|---|
a query window with after and before, or first and last | A query window cannot combine after with before, or first with last |
| a query cursor whose row is gone, or hidden from the caller | The query cursor no longer resolves to a row |
| a query cursor of another order, or one this server did not make | The query cursor is not one this server minted for this order |
| a relation window's cursor with more than one parent | Relation "<field>" cursor needs a single parent |
| a relation window's cursor whose row is gone, or hidden from the caller | Relation "<field>" cursor no longer resolves |
| an operation id reused with a different mutation, keys, or input | Operation "<id>" cannot be sent again with another mutation, keys or input… |
The full operation-id error ends with : a retry sends the same ones. A declared refusal (Taken, Conflict, Unmet, Invalid, Referenced) is
not a failure and travels as its own value.