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
When retrieving data directly from the database/data source, the fields is_archived and is_draft are both 'f' (false), but these dashboards/queries still cannot be found or searched in the Redash web interface. What could be the reason? #7705
The two fields is_archived (whether archived) and is_draft (whether draft) — are these fields automatically updated by the system?
Why is it that these items can no longer be found/searched in the Redash web interface, but they still exist in the database (SQL source data), and both fields are set to 'f' (false)?
Additionally, when querying by excluding items where data_source_id is empty, and even after joining the dashboards table with the query_results table to filter out records with empty data_source_id, some dashboards still have is_archived = 'f' and is_draft = 'f', but they still cannot be found in the UI. What is the reason for this?
In Redash version 8.0.0+b32245, in the PostgreSQL database:
queries table (query table)
dashboards table (dashboard table)
The two fields is_archived (whether archived) and is_draft (whether draft) — are these fields automatically updated by the system?
Why is it that these items can no longer be found/searched in the Redash web interface, but they still exist in the database (SQL source data), and both fields are set to 'f' (false)?
Additionally, when querying by excluding items where data_source_id is empty, and even after joining the dashboards table with the query_results table to filter out records with empty data_source_id, some dashboards still have is_archived = 'f' and is_draft = 'f', but they still cannot be found in the UI. What is the reason for this?