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 `ExecuteSqlMetadata.Types.Status` enum in the AlloyDB v1alpha API defines the possible outcomes of SQL execution."],["Possible status values include `Error`, indicating at least one SQL statement resulted in an error and all side effects were rolled back, with the error message being provided."],["The `Ok` status signifies that all SQL statements were completed successfully, without errors."],["`Partial` status indicates a successful execution, although with incomplete results, including a message field with details on the truncation."],["`Unspecified` status represents that the final status of the execution is unknown."]]],[]]
