feat: Update result_set.proto to return undeclared parameters in ExecuteSql API

Google APIs · copybara-github · commit cb6fbe878447 · 2022-10-10T02:05:11.000-07:00
PiperOrigin-RevId: 480025979
diff --git a/google/spanner/v1/result_set.proto b/google/spanner/v1/result_set.proto
@@ -174,6 +174,18 @@ message ResultSetMetadata {
   // If the read or SQL query began a transaction as a side-effect, the
   // information about the new transaction is yielded here.
   Transaction transaction = 2;
+
+  // A SQL query can be parameterized. In PLAN mode, these parameters can be
+  // undeclared. This indicates the field names and types for those undeclared
+  // parameters in the SQL query. For example, a SQL query like `"SELECT * FROM
+  // Users where UserId = @userId and UserName = @userName "` could return a
+  // `undeclared_parameters` value like:
+  //
+  //     "fields": [
+  //       { "name": "UserId", "type": { "code": "INT64" } },
+  //       { "name": "UserName", "type": { "code": "STRING" } },
+  //     ]
+  StructType undeclared_parameters = 3;
 }
 
 // Additional statistics about a [ResultSet][google.spanner.v1.ResultSet] or [PartialResultSet][google.spanner.v1.PartialResultSet].
