Error during SQL execution. Atleast 1 SQL statement execution resulted in
a error. Side effects of other statements are rolled back. The "message"
field will contain human readable error given by Postgres of the first
bad SQL statement. SQL execution errors don't constitute API errors as
defined in https://google.aip.dev/193 but will be returned as part of
this message.
Ok
No error during SQL execution i.e. All SQL statements ran to completion.
The "message" will be empty.
Partial
Same as OK, except indicates that only partial results were
returned. The "message" field will contain details on why results were
truncated.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["The document provides reference documentation for the `ExecuteSqlMetadata.Types.Status` enum within the AlloyDB v1 API."],["This enum defines possible statuses for SQL execution, including `Error`, `Ok`, `Partial`, and `Unspecified`."],["The latest version of this documentation is for version 1.9.0, but documentation for versions 1.0.0 through 1.8.0 are also accessible."],["Each Status field has a Description section explaining what the status entails, such as errors, partial success, full success, and unknown."]]],[]]
