Google \ Cloud \ AlloyDb \ V1 \ ExecuteSqlMetadata
Methods
static::name
Parameter
Name
Description
value
mixed
static::value
Parameter
Name
Description
name
mixed
Constants
STATUS_UNSPECIFIED
Value: 0
The status is unknown.
Generated from protobuf enumSTATUS_UNSPECIFIED = 0;
OK
Value: 1
No error during SQL execution i.e. All SQL statements ran to completion.
The "message" will be empty.
Generated from protobuf enumOK = 1;
PARTIAL
Value: 2
Same as OK, except indicates that only partial results were
returned. The "message" field will contain details on why results were
truncated.
Generated from protobuf enumPARTIAL = 2;
ERROR
Value: 3
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 inhttps://google.aip.dev/193but will be returned as part of
this message.
[[["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-09-04 UTC."],[],[],null,["# Google Cloud AlloyDB for PostgreSQL V1 Client - Class Status (1.4.1)\n\nVersion latestkeyboard_arrow_down\n\n- [1.4.1 (latest)](/php/docs/reference/cloud-alloydb/latest/V1.ExecuteSqlMetadata.Status)\n- [1.4.0](/php/docs/reference/cloud-alloydb/1.4.0/V1.ExecuteSqlMetadata.Status)\n- [1.3.0](/php/docs/reference/cloud-alloydb/1.3.0/V1.ExecuteSqlMetadata.Status)\n- [1.2.0](/php/docs/reference/cloud-alloydb/1.2.0/V1.ExecuteSqlMetadata.Status)\n- [1.1.3](/php/docs/reference/cloud-alloydb/1.1.3/V1.ExecuteSqlMetadata.Status)\n- [1.0.0](/php/docs/reference/cloud-alloydb/1.0.0/V1.ExecuteSqlMetadata.Status)\n- [0.10.3](/php/docs/reference/cloud-alloydb/0.10.3/V1.ExecuteSqlMetadata.Status)\n- [0.9.0](/php/docs/reference/cloud-alloydb/0.9.0/V1.ExecuteSqlMetadata.Status)\n- [0.8.0](/php/docs/reference/cloud-alloydb/0.8.0/V1.ExecuteSqlMetadata.Status)\n- [0.7.1](/php/docs/reference/cloud-alloydb/0.7.1/V1.ExecuteSqlMetadata.Status)\n- [0.6.0](/php/docs/reference/cloud-alloydb/0.6.0/V1.ExecuteSqlMetadata.Status)\n- [0.5.0](/php/docs/reference/cloud-alloydb/0.5.0/V1.ExecuteSqlMetadata.Status)\n- [0.4.0](/php/docs/reference/cloud-alloydb/0.4.0/V1.ExecuteSqlMetadata.Status)\n- [0.3.0](/php/docs/reference/cloud-alloydb/0.3.0/V1.ExecuteSqlMetadata.Status)\n- [0.2.1](/php/docs/reference/cloud-alloydb/0.2.1/V1.ExecuteSqlMetadata.Status)\n- [0.1.3](/php/docs/reference/cloud-alloydb/0.1.3/V1.ExecuteSqlMetadata.Status) \nReference documentation and code samples for the Google Cloud AlloyDB for PostgreSQL V1 Client class Status.\n\nStatus contains all valid Status a SQL execution can end up in.\n\nProtobuf type `google.cloud.alloydb.v1.ExecuteSqlMetadata.Status`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ AlloyDb \\\\ V1 \\\\ ExecuteSqlMetadata\n\nMethods\n-------\n\n### static::name\n\n### static::value\n\nConstants\n---------\n\n### STATUS_UNSPECIFIED\n\n Value: 0\n\nThe status is unknown.\n\nGenerated from protobuf enum `STATUS_UNSPECIFIED = 0;`\n\n### OK\n\n Value: 1\n\nNo error during SQL execution i.e. All SQL statements ran to completion.\n\nThe \"message\" will be empty.\n\nGenerated from protobuf enum `OK = 1;`\n\n### PARTIAL\n\n Value: 2\n\nSame as OK, except indicates that only partial results were\nreturned. The \"message\" field will contain details on why results were\ntruncated.\n\nGenerated from protobuf enum `PARTIAL = 2;`\n\n### ERROR\n\n Value: 3\n\nError during SQL execution. Atleast 1 SQL statement execution resulted in\na error. Side effects of other statements are rolled back. The \"message\"\nfield will contain human readable error given by Postgres of the first\nbad SQL statement. SQL execution errors don't constitute API errors as\ndefined in \u003chttps://google.aip.dev/193\u003e but will be returned as part of\nthis message.\n\nGenerated from protobuf enum `ERROR = 3;`"]]