mirror of
https://github.com/featurebasedb/featurebase.git
synced 2026-08-28 02:44:59 +00:00
10b60f5d51
If we don't set an epoch, we get a cryptic message on the console. Note, this message isn't logged properly, it doesn't use the logger, it uses the `log` package. 2023/02/09 11:07:23 ERROR: converting timestamp options for end_time: checking overflow: custom epoch too far from Unix epoch: 0001-01-01 00:00:00 +0000 UTC Because this uses the log package, it doesn't go to the same place as other messages, making it a pain to debug. The underlying problem is that a timestamp can't just have a zero value for its epoch. So, we set a default epoch of 0 Unix Time. We should possibly revisit the question of whether the conversion in the top-level schema.go should handle an epoch which IsZero, but I'm not sure what "base" should be in that case. In practice, all existing usages except this one are specifying time.Unix(0, 0) already. |
||
|---|---|---|
| .. | ||
| parser | ||
| planner | ||
| test | ||
| errors.go | ||
| interfaces.go | ||
| main_test.go | ||
| sql_complex_test.go | ||
| sql_test.go | ||