As I recall there might have been the desire to permit 64-bit
representation of SECOND and MILLI time values, but I would opt for
YAGNI (until we actually do) and deprecate this bit width field in
Schema.fbs (we shouldn't outright remove it -- for backwards
compatibility -- unless it's actively
In the flatbuffer schema what is the purpose of bit width in "table Time"
[1] based on the documentation it sounds like bit-width is fully determined
by TimeUnit? In other cases (e.g. Date) we don't have a similar field.
Thanks,
Micah
[1]
