Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to set a default column names for the primary time column in the datasource config. for Date and Timestamp, This would be used by the $timeFilter etc. macros unless overridden in the query builder #495

Closed
Slach opened this issue Nov 20, 2023 · 2 comments · Fixed by #567
Assignees
Labels
p1 Priority 1
Milestone

Comments

@Slach
Copy link
Collaborator

Slach commented Nov 20, 2023

add to ConfigEditor

  • datetime
  • datetime64
  • uint32
  • date / date32
@Slach Slach added this to the 3.0.0 milestone Nov 20, 2023
@Slach Slach self-assigned this Nov 20, 2023
@svb-alt svb-alt added the p3 Priority 3 label Apr 1, 2024
@Slach Slach modified the milestones: 3.1.0, 3.2.0 Apr 29, 2024
@Slach Slach added p1 Priority 1 and removed p3 Priority 3 labels Apr 29, 2024
@oplehto
Copy link

oplehto commented May 13, 2024

What would be really fantastic would be to able to define multiple default time columns which could be used in order of precedence.

For example, if the config has _time, _time64 as default time columns then the _time column would be used if found (and is a suitable type). If not, then _time64 would be searched for. In case both columns are present, then the first one in the list would be used.

@Slach Slach changed the title Ability to set a default column name for the primary time column in the datasource config. This would be used by the $timeFilter etc. macros unless overridden in the query builder Ability to set a default column names for the primary time column in the datasource config. for Date and Timestamp, This would be used by the $timeFilter etc. macros unless overridden in the query builder May 18, 2024
@Slach
Copy link
Collaborator Author

Slach commented Jun 14, 2024

What would be really fantastic would be to able to define multiple default time columns which could be used in order of precedence.

@oplehto
No, it will define only only one field for each related field type per connection

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p1 Priority 1
Projects
None yet
3 participants