Skip to content

Spanner should have helpful aliases for param types #3364

Description

@theacodes

Having to do:

fromgoogle.cloudimportspannerfromgoogle.cloud.proto.spanner.v1importtype_pb2instance=spanner_client.instance(instance_id)
database=instance.database(database_id)
params= {
'start': start,
'end': end
}
param_types= {
'start': type_pb2.Type(code=type_pb2.STRING),
'end': type_pb2.Type(code=type_pb2.STRING)
}
results=database.execute_sql(
"SELECT AlbumId, AlbumTitle, MarketingBudget ""FROM Albums@{FORCE_INDEX=AlbumsByAlbumTitle} ""WHERE AlbumTitle >= @start AND AlbumTitle < @end",
params=params, param_types=param_types)

Is rather awkward, it would be much more friendly to have:

fromgoogle.cloudimportspannerinstance=spanner_client.instance(instance_id)
database=instance.database(database_id)
params= {
'start': start,
'end': end
}
param_types= {
'start': spanner.ParamTypes.STRING,
'end': spanner.ParamTypes.STRING
}
results=database.execute_sql(
"SELECT AlbumId, AlbumTitle, MarketingBudget ""FROM Albums@{FORCE_INDEX=AlbumsByAlbumTitle} ""WHERE AlbumTitle >= @start AND AlbumTitle < @end",
params=params, param_types=param_types)

or similar

Metadata

Metadata

Assignees

Labels

api: spannerIssues related to the Spanner API.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions