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 }}
This repository has been archived by the owner on Feb 21, 2024. It is now read-only.
time fields automatically create/populate a standard view which represents all setbits with no time value taken into consideration (like a set field). It's possible that a user wouldn't need that data. In that case, we could give the user the option to suppress that view (i.e. improve write performance and reduce storage requirements).
Success criteria (What criteria will consider this ticket closeable?)
I guess this would mean modifying OptFieldTypeTime() to include this additional option. Note that that would be an API change. We could also provide a separate option, but that may be confusing.
The text was updated successfully, but these errors were encountered:
Description
time
fields automatically create/populate astandard
view which represents all setbits with no time value taken into consideration (like aset
field). It's possible that a user wouldn't need that data. In that case, we could give the user the option to suppress that view (i.e. improve write performance and reduce storage requirements).Success criteria (What criteria will consider this ticket closeable?)
I guess this would mean modifying
OptFieldTypeTime()
to include this additional option. Note that that would be an API change. We could also provide a separate option, but that may be confusing.The text was updated successfully, but these errors were encountered: