Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BigQuery: Add enum with allowed data types for use in Schema #7632

Closed
tswast opened this issue Apr 1, 2019 · 2 comments · Fixed by #9040
Closed

BigQuery: Add enum with allowed data types for use in Schema #7632

tswast opened this issue Apr 1, 2019 · 2 comments · Fixed by #9040
Assignees
Labels
api: bigquery Issues related to the BigQuery API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@tswast
Copy link
Contributor

tswast commented Apr 1, 2019

I received a feature request internally for an enum with allowed data types for use in SchemaField.

The string values should match the names of the BigQuery legacy SQL data types, but we could potentially add additional constants using the standard SQL data type names, but still the legacy SQL string value.

@tswast tswast added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. api: bigquery Issues related to the BigQuery API. labels Apr 1, 2019
@tswast
Copy link
Contributor Author

tswast commented Aug 14, 2019

We might already have such a list of (legacy) data types somewhere? It'd be nice to have an enum for these, similar to how we have one for standard SQL now.

@tswast
Copy link
Contributor Author

tswast commented Aug 14, 2019

Standard SQL version: google.cloud.bigquery.enums.StandardSqlDataTypes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquery Issues related to the BigQuery API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants