I have updated the query for issue #3132 to match version 10.

[keitoueno]

What type of PR is this?

• Refactor
• Feature
• Bug Fix
• New Query Runner (Data Source)
• New Alert Destination
• Other

Description

I am writing a lot of queries in Python data sources.
Most of the time, I use Python's "execute_query" to directly specify the data source and query.

However, recently I have had too many queries, so I wanted to use one query like a module. Therefore, I found a solution in issue #3132 and made modifications to match redash version 10. Please review and approve it.

How is this tested?

• Unit tests (pytest, jest)
• E2E Tests (Cypress)
• Manually
• N/A

Query A needs to be created as follows. The datasource used is MySQL.

SELECT customer_id FROM customer WHERE customer_id = {{customer_id}}
Note: The query ID for this query is 2 in my local Redash environment.

Query B needs to be created as follows.

data = execute_by_query_id(2, {"customer_id": "1234567"})
result = {}
for rows1 in data['rows']:
    add_result_row(result, {
        'customer_id' : rows1['customer_id'],
    })

add_result_column(result, 'customer_id', '', 'string')

The result for Query B is the data obtained from Query A (query ID 2).

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

[justinclift]

I'm not really understanding how this is different from the existing ability to run SQL on the result of a previous query.

https://redash.io/help/user-guide/querying/query-results-data-source

Is it something to do with the use of parameters?

[justinclift]

Probably not good to leave commented out code around like this. 😉

[konnectr]

I understand the code was taken from here #3132

[keitoueno]

I'm not really understanding how this is different from the existing ability to run SQL on the result of a previous query.

https://redash.io/help/user-guide/querying/query-results-data-source

Is it something to do with the use of parameters?

Thank you for your reply. Yes, that's correct. With this customization, you will be able to call a query created in Python with arguments from different resources. In the example, it shows using "customer_id," but in many cases, you might use it for date-based calls. In fact, what I'm using it for is creating queries called from resources like Athena or RDS in Python and wanting to call them from different resources.