You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support both seconds from epoch and timestamp string #1382
If someone already has a timestamp string, we shouldn't force them to convert it to datetime.datetime so that we can in turn convert that into seconds. (Inspired by #1381.)
TIMESTAMP data types can be described in two ways: UNIX timestamps or calendar datetimes. BigQuery stores TIMESTAMP data internally as a UNIX timestamp with microsecond precision.
so we could allow the user to just pass a string and we "take their word for it" that it's a valid datetime. Since Table.insert_data returns a list of errors anyhow, we wouldn't have to do much/anything to enforce this.
Activity
Allow timestamp strings in 'Table.insert_data'.
chore: add `transport` argument to py_gapic_library rule to make its …
Fix: Less restrictive content-type header check for google authentica…
chore(deps): update all dependencies (#1382)
feat(spanner): add new change_stream.proto (#1382)
docs: migrate code from googleapis/python-bigquery (#18303)