public static final class ResultSetMetadata.Builder extends GeneratedMessageV3.Builder<ResultSetMetadata.Builder> implements ResultSetMetadataOrBuilder
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
public static final Descriptors.Descriptor getDescriptor()
Methods
public ResultSetMetadata.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)
public ResultSetMetadata build()
public ResultSetMetadata buildPartial()
public ResultSetMetadata.Builder clear()
public ResultSetMetadata.Builder clearField(Descriptors.FieldDescriptor field)
public ResultSetMetadata.Builder clearOneof(Descriptors.OneofDescriptor oneof)
public ResultSetMetadata.Builder clearRowType()
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;
public ResultSetMetadata.Builder clearTransaction()
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;
public ResultSetMetadata.Builder clearUndeclaredParameters()
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;
public ResultSetMetadata.Builder clone()
public ResultSetMetadata getDefaultInstanceForType()
public Descriptors.Descriptor getDescriptorForType()
public StructType getRowType()
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;
public StructType.Builder getRowTypeBuilder()
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;
public StructTypeOrBuilder getRowTypeOrBuilder()
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;
public Transaction getTransaction()
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;
public Transaction.Builder getTransactionBuilder()
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;
public TransactionOrBuilder getTransactionOrBuilder()
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;
public StructType getUndeclaredParameters()
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. |
public StructType.Builder getUndeclaredParametersBuilder()
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;
public StructTypeOrBuilder getUndeclaredParametersOrBuilder()
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;
public boolean hasRowType()
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. |
public boolean hasTransaction()
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. |
public boolean hasUndeclaredParameters()
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. |
protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
public final boolean isInitialized()
public ResultSetMetadata.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
public ResultSetMetadata.Builder mergeFrom(Message other)
| Parameter |
|---|
| Name | Description |
other | Message
|
Overridespublic ResultSetMetadata.Builder mergeFrom(ResultSetMetadata other)
public ResultSetMetadata.Builder mergeRowType(StructType value)
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;
public ResultSetMetadata.Builder mergeTransaction(Transaction value)
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;
public ResultSetMetadata.Builder mergeUndeclaredParameters(StructType value)
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;
public final ResultSetMetadata.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
public ResultSetMetadata.Builder setField(Descriptors.FieldDescriptor field, Object value)
public ResultSetMetadata.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
public ResultSetMetadata.Builder setRowType(StructType value)
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;
public ResultSetMetadata.Builder setRowType(StructType.Builder builderForValue)
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;
public ResultSetMetadata.Builder setTransaction(Transaction value)
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;
public ResultSetMetadata.Builder setTransaction(Transaction.Builder builderForValue)
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;
public ResultSetMetadata.Builder setUndeclaredParameters(StructType value)
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;
public ResultSetMetadata.Builder setUndeclaredParameters(StructType.Builder builderForValue)
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;
public final ResultSetMetadata.Builder setUnknownFields(UnknownFieldSet unknownFields)