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
Associating the value with the type is reasonable, but the current solution break the data structure and bring inconvenience.
I expect table.insert({time_ts: BigQuery.timestamp('2012-12-20)}) should work with schema "time_ts: TIMESTAMP" but in fact I got "This field is not a record." because what it actually send is {"time_ts":{"value":"2012-12-20"}} instead of {"time_ts":"2012-12-20"}.
The text was updated successfully, but these errors were encountered:
stephenplusplus
added
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
labels
Nov 10, 2017
Related issue: #2479
Associating the value with the type is reasonable, but the current solution break the data structure and bring inconvenience.
I expect
table.insert({time_ts: BigQuery.timestamp('2012-12-20)})
should work with schema "time_ts: TIMESTAMP" but in fact I got "This field is not a record." because what it actually send is{"time_ts":{"value":"2012-12-20"}}
instead of{"time_ts":"2012-12-20"}
.The workaround I currently use is
Environment details
The text was updated successfully, but these errors were encountered: