The date/time data type is important when using components or displaying information that relies on dates and times.
The Date picker component, for example, can utilize the date field. Dates within Budibase comply with ISO8601 formating, e.g.
2020-09-24T13:12:04.622Z. Thankfully, the date picker makes data entry easier.
- First, click the
- Give your column a name
- Choose date/time as your data type
- Enter some optional constraints
You can provide an earliest and latest date within your date/time column. This allows you to enforce a constraint such that dates added must fall before the latest and after the earliest dates specified.
As with all other fields you can make it required.
These constraints can easily be edited after creation by hovering over the date field and clicking the pencil icon.
When this option is checked, the values selected in date pickers will be saved exactly as they are represented into the target database. Regardless of the timezone the browser is in, you will always see the same exact timestamp when this option is selected.
As an example, here is a snippet of a table where the browsers locale was changed to 3 different timezones and the time 12:00 was picked in each. You can see that the column "BB no timezone" (which has Ignore time zones enabled) will always show the same time, whereas the "BB normal" column (where the flag is toggled off) reflects the browser timezone changes.
It is possible, but not recommended, to change the Ignore time zones flag on tables that already have dates with timezones. Changing this flag does not change existing data, but it will change how your existing data is presented in the browser.
By default this setting is toggled off.
This setting is also available for PostgreSQL and MySQL tables.
Updated about 1 month ago