publicstaticfinalclassResultSetMetadata.BuilderextendsGeneratedMessageV3.Builder<ResultSetMetadata.Builder>implementsResultSetMetadataOrBuilder
Metadata about a ResultSet or PartialResultSet.
Protobuf type google.spanner.v1.ResultSetMetadata
Inherited Members
com.google.protobuf.GeneratedMessageV3.Builder.getUnknownFieldSetBuilder()
com.google.protobuf.GeneratedMessageV3.Builder.internalGetMapFieldReflection(int)
com.google.protobuf.GeneratedMessageV3.Builder.internalGetMutableMapFieldReflection(int)
com.google.protobuf.GeneratedMessageV3.Builder.mergeUnknownLengthDelimitedField(int,com.google.protobuf.ByteString)
com.google.protobuf.GeneratedMessageV3.Builder.mergeUnknownVarintField(int,int)
com.google.protobuf.GeneratedMessageV3.Builder.parseUnknownField(com.google.protobuf.CodedInputStream,com.google.protobuf.ExtensionRegistryLite,int)
com.google.protobuf.GeneratedMessageV3.Builder.setUnknownFieldSetBuilder(com.google.protobuf.UnknownFieldSet.Builder)
Static Methods
publicstaticfinalDescriptors.DescriptorgetDescriptor()
Methods
publicResultSetMetadata.BuilderaddRepeatedField(Descriptors.FieldDescriptorfield,Objectvalue)
publicResultSetMetadatabuild()
publicResultSetMetadatabuildPartial()
publicResultSetMetadata.Builderclear()
publicResultSetMetadata.BuilderclearField(Descriptors.FieldDescriptorfield)
publicResultSetMetadata.BuilderclearOneof(Descriptors.OneofDescriptoroneof)
publicResultSetMetadata.BuilderclearRowType()
Indicates the field names and types for the rows in the result set. For example, a SQL query like "SELECT UserId, UserName FROM Users" could return a row_type value like:
"fields": [ { "name": "UserId", "type": { "code": "INT64" } }, { "name": "UserName", "type": { "code": "STRING" } }, ]
.google.spanner.v1.StructType row_type = 1;
publicResultSetMetadata.BuilderclearTransaction()
If the read or SQL query began a transaction as a side-effect, the information about the new transaction is yielded here.
.google.spanner.v1.Transaction transaction = 2;
publicResultSetMetadata.BuilderclearUndeclaredParameters()
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" } }, ]
.google.spanner.v1.StructType undeclared_parameters = 3;
publicResultSetMetadata.Builderclone()
publicResultSetMetadatagetDefaultInstanceForType()
publicDescriptors.DescriptorgetDescriptorForType()
publicStructTypegetRowType()
Indicates the field names and types for the rows in the result set. For example, a SQL query like "SELECT UserId, UserName FROM Users" could return a row_type value like:
"fields": [ { "name": "UserId", "type": { "code": "INT64" } }, { "name": "UserName", "type": { "code": "STRING" } }, ]
.google.spanner.v1.StructType row_type = 1;
publicStructType.BuildergetRowTypeBuilder()
Indicates the field names and types for the rows in the result set. For example, a SQL query like "SELECT UserId, UserName FROM Users" could return a row_type value like:
"fields": [ { "name": "UserId", "type": { "code": "INT64" } }, { "name": "UserName", "type": { "code": "STRING" } }, ]
.google.spanner.v1.StructType row_type = 1;
publicStructTypeOrBuildergetRowTypeOrBuilder()
Indicates the field names and types for the rows in the result set. For example, a SQL query like "SELECT UserId, UserName FROM Users" could return a row_type value like:
"fields": [ { "name": "UserId", "type": { "code": "INT64" } }, { "name": "UserName", "type": { "code": "STRING" } }, ]
.google.spanner.v1.StructType row_type = 1;
publicTransactiongetTransaction()
If the read or SQL query began a transaction as a side-effect, the information about the new transaction is yielded here.
.google.spanner.v1.Transaction transaction = 2;
publicTransaction.BuildergetTransactionBuilder()
If the read or SQL query began a transaction as a side-effect, the information about the new transaction is yielded here.
.google.spanner.v1.Transaction transaction = 2;
publicTransactionOrBuildergetTransactionOrBuilder()
If the read or SQL query began a transaction as a side-effect, the information about the new transaction is yielded here.
.google.spanner.v1.Transaction transaction = 2;
publicStructTypegetUndeclaredParameters()
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" } }, ]
.google.spanner.v1.StructType undeclared_parameters = 3;
| Returns |
|---|
| Type | Description |
StructType | The undeclaredParameters. |
publicStructType.BuildergetUndeclaredParametersBuilder()
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" } }, ]
.google.spanner.v1.StructType undeclared_parameters = 3;
publicStructTypeOrBuildergetUndeclaredParametersOrBuilder()
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" } }, ]
.google.spanner.v1.StructType undeclared_parameters = 3;
publicbooleanhasRowType()
Indicates the field names and types for the rows in the result set. For example, a SQL query like "SELECT UserId, UserName FROM Users" could return a row_type value like:
"fields": [ { "name": "UserId", "type": { "code": "INT64" } }, { "name": "UserName", "type": { "code": "STRING" } }, ]
.google.spanner.v1.StructType row_type = 1;
| Returns |
|---|
| Type | Description |
boolean | Whether the rowType field is set. |
publicbooleanhasTransaction()
If the read or SQL query began a transaction as a side-effect, the information about the new transaction is yielded here.
.google.spanner.v1.Transaction transaction = 2;
| Returns |
|---|
| Type | Description |
boolean | Whether the transaction field is set. |
publicbooleanhasUndeclaredParameters()
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" } }, ]
.google.spanner.v1.StructType undeclared_parameters = 3;
| Returns |
|---|
| Type | Description |
boolean | Whether the undeclaredParameters field is set. |
protectedGeneratedMessageV3.FieldAccessorTableinternalGetFieldAccessorTable()
publicfinalbooleanisInitialized()
publicResultSetMetadata.BuildermergeFrom(CodedInputStreaminput,ExtensionRegistryLiteextensionRegistry)
publicResultSetMetadata.BuildermergeFrom(Messageother)
| Parameter |
|---|
| Name | Description |
other | Message
|
OverridespublicResultSetMetadata.BuildermergeFrom(ResultSetMetadataother)
publicResultSetMetadata.BuildermergeRowType(StructTypevalue)
Indicates the field names and types for the rows in the result set. For example, a SQL query like "SELECT UserId, UserName FROM Users" could return a row_type value like:
"fields": [ { "name": "UserId", "type": { "code": "INT64" } }, { "name": "UserName", "type": { "code": "STRING" } }, ]
.google.spanner.v1.StructType row_type = 1;
publicResultSetMetadata.BuildermergeTransaction(Transactionvalue)
If the read or SQL query began a transaction as a side-effect, the information about the new transaction is yielded here.
.google.spanner.v1.Transaction transaction = 2;
publicResultSetMetadata.BuildermergeUndeclaredParameters(StructTypevalue)
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" } }, ]
.google.spanner.v1.StructType undeclared_parameters = 3;
publicfinalResultSetMetadata.BuildermergeUnknownFields(UnknownFieldSetunknownFields)
publicResultSetMetadata.BuildersetField(Descriptors.FieldDescriptorfield,Objectvalue)
publicResultSetMetadata.BuildersetRepeatedField(Descriptors.FieldDescriptorfield,intindex,Objectvalue)
publicResultSetMetadata.BuildersetRowType(StructTypevalue)
Indicates the field names and types for the rows in the result set. For example, a SQL query like "SELECT UserId, UserName FROM Users" could return a row_type value like:
"fields": [ { "name": "UserId", "type": { "code": "INT64" } }, { "name": "UserName", "type": { "code": "STRING" } }, ]
.google.spanner.v1.StructType row_type = 1;
publicResultSetMetadata.BuildersetRowType(StructType.BuilderbuilderForValue)
Indicates the field names and types for the rows in the result set. For example, a SQL query like "SELECT UserId, UserName FROM Users" could return a row_type value like:
"fields": [ { "name": "UserId", "type": { "code": "INT64" } }, { "name": "UserName", "type": { "code": "STRING" } }, ]
.google.spanner.v1.StructType row_type = 1;
publicResultSetMetadata.BuildersetTransaction(Transactionvalue)
If the read or SQL query began a transaction as a side-effect, the information about the new transaction is yielded here.
.google.spanner.v1.Transaction transaction = 2;
publicResultSetMetadata.BuildersetTransaction(Transaction.BuilderbuilderForValue)
If the read or SQL query began a transaction as a side-effect, the information about the new transaction is yielded here.
.google.spanner.v1.Transaction transaction = 2;
publicResultSetMetadata.BuildersetUndeclaredParameters(StructTypevalue)
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" } }, ]
.google.spanner.v1.StructType undeclared_parameters = 3;
publicResultSetMetadata.BuildersetUndeclaredParameters(StructType.BuilderbuilderForValue)
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" } }, ]
.google.spanner.v1.StructType undeclared_parameters = 3;
publicfinalResultSetMetadata.BuildersetUnknownFields(UnknownFieldSetunknownFields)
