Query Referencing

Easily reference results from exiting queries!

Query Referencing allows you to streamline your analysis workflow by reusing the results of previously executed queries as data sources for new queries. This feature enhances query organization, promotes reusability of complex result sets, and significantly boosts query performance.

Overview

This section will cover:

1. How to reference a query?

2. How to leverage query referencing to speed up parameter runs?

3. How to decide which query to reference?

4. Limitations

---

How to reference a query?

1. Identify the Query:

   1. Navigate to the desired query and click "Copy Reference" button to obtain the query ID.

      
   2. To reference your own query, find the query you want to reference under "My Work". Click the 3-dot menu, and select "Add to Query".

      
2. Reference the Query:

   • In your new query, use the following syntax to reference the query:

     SELECT * 
     FROM $query('query_id')

3. Join with other tables:

   • You can join the referenced query with other tables in your dataset:

     SELECT * 
     FROM bitcoin.core.fact_transactions t
     JOIN $query('query_id') AS my_query 
       ON my_query.blockheight = t.blockheight

---

Leveraging Query Referencing for Performance Optimization

A significant advantages of Query Referencing is its ability to dramatically improve the performance of parameterized queries.

With Query Referencing

1. Pre-calculate the 100,000 most relevant addresses:

   select 
       from_address,
       count(1) as n_tx   -- can safely count(1) b/c this table is 1 row per tx_hash
   from ethereum.core.fact_transactions 
   where block_timestamp >= '2024-01-01'
   group by from_address
   having n_tx < 20001 -- assume > 20k is bots 
   order by n_tx desc 
   limit 100000;

2. Reference the pre-calculated result:

   select * from 
   $query('0a0d54ca-f8de-43fe-8e5f-c270272982f9') -- query id taken from studio URL
   where from_address = '{{wallet_address}}';

By pre-calculating the relevant addresses and referencing the result, you can significantly improve query performance, especially when dealing with large datasets and frequent parameter changes.

Without Query Referencing

This approach requires the query to be re-executed for each user, leading to potential performance bottlenecks.

select 
from_address, 
count(tx_hash) as n_tx 
from base.core.fact_transactions
where block_timestamp >= '2024-01-01'
and from_address = '{{wallet_address}}'

---

How to decide which query to reference?

1. Do Your Own Research (DYOR): Always verify the logic and accuracy of the referenced query.

Since all public queries can be referenced, make sure you trace query dependencies! Hover over any $query('query_id') and click on the query title in the popover to view all information about the underlying query.

1. Consider Query Refresh Rates: Ensure that the referenced query is refreshed at an appropriate interval to provide up-to-date results.

• To ensure up-to-date results, set a "Refresh Rate" on your base query

• Any new query referencing the results will automatically use the refreshed data

• Refreshes follow standard query refresh capabilities

1. Understand Cache Expiration: Be aware of the cache duration and expiration rules for referenced queries.

• Results are cached and available for 24 hours by default

• Each reference within the 24-hour window extends availability by another 24 hours

• Maximum cache duration is 31 days

---

Limitations

Base queries that utilize parameters will always execute with their default values when referenced. Currently, there’s no mechanism to dynamically pass parameters into the $query() function. It is best to avoid using parameters in your base queries.