Adding a time column in the column configurator can eventually duplicate the time column

[pauldambra]

Bug description

The events table adds a time column even if one isn't set in the column configurator

Setting a time column (if a time property is available on events.) initially behaves correctly but on repeated save will duplicate the time column

Expected behavior

you don't get two time columns

How to reproduce

1. use column configurator to add a time column
2. navigate to another tab
3. come back to the events page
4. the table will display correctly
5. open the column configurator
6. it will include the time column added previously
7. click save
8. two time columns

Environment

• PostHog Cloud
• self-hosted PostHog (ClickHouse-based), version/commit: please provide
• self-hosted PostHog (Postgres-based, legacy), version/commit: please provide

Additional context

Thank you for your bug report – we love squashing them!

[pauldambra]

choose $time for a column in the configurator

both the tableConfigLogic and columnConfiguratorLogic show $time as one of the selected columns.

Navigate away and then back. The columns are back to default in the view

the tableConfigLogic shows 'DEFAULTas the selected columns. ThecolumnConfiguratorLogicshowstime` as one of the selected columns.

time is the key for the timestamp column so its value is duplicated