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
Right now, the sqlite dataFunc scans the value for every column into a []byte, regardless of its underlying type. This is convenient for our data processing functions -- but does mean that we hit some weird edge cases. For example, float64 date columns will be formatted in scientific notation (per https://cs.opensource.google/go/go/+/refs/tags/go1.24.0:src/database/sql/convert.go;l=532).
We may want to revisit how we're scanning in the data to handle these use cases a little more cleanly.
Right now, the sqlite dataFunc scans the value for every column into a
[]byte
, regardless of its underlying type. This is convenient for our data processing functions -- but does mean that we hit some weird edge cases. For example, float64 date columns will be formatted in scientific notation (per https://cs.opensource.google/go/go/+/refs/tags/go1.24.0:src/database/sql/convert.go;l=532).We may want to revisit how we're scanning in the data to handle these use cases a little more cleanly.
See: https://github.com/kolide/launcher/blob/main/ee/katc/sqlite.go
The text was updated successfully, but these errors were encountered: