1

We have 900+ queries in production. So many queries make it difficult for us to modify the indicator definition quickly and accurately.
What existing functions or unimplemented ideas can improve this problem, and we will try to implement them

2 Likes
2

I’m also very interested in managing our queries. Any tips on what you are already doing?

3

A scheme under consideration: extract field names from the select statement as candidate indicators, and provide a page to help complete the conversion between candidate indicators and formal indicators

4

Great idea.

Regex is probably your friend.

I wrote this script that does this for table names, so users can see which tables are being queried by Redash.

In Python you could make good use of sqlparse instead of regex since it will automatically detect field names from SELECT queries.

The Redash interaction here is simple: fetch queries in bulk from the API and POST any changes back.