Running SQL queries

Whale also enables users to run queries from command-line, against both plain SQL files as well as within markdown files, enabling notebook-style behavior.

Supported connections: BigQuery, Postgres, Presto, Redshift, Snowflake
Executing SQL files
Whale exposes a direct line into SQLAlchemy against connections defined in ~/.whale/config/connections.yaml through the wh run command.
1
wh run filename.sql -w warehouse_name
Copied!
If the -w flag is not given, the first warehouse in your connections.yaml file will be used.
If there are multiple warehouses with the same warehouse_name the credentials from the first matching warehouse_name encountered will be used.
Note: this only works for (a) direct connections to warehouses (not the Hive metastore) and (b) connections where permissions allow for query runs.
Jinja templating
wh run also supports Jinja2 templating -- for more information on how to set this up, see Jinja2 templating.
Saving results as comments
If you'd like to store your results automatically as comments within your .sql file, you can add --!wh-run to any SQL file (on its own line) and any wh run execution will automatically string replace this line with the results of the query execution.
For example, the following sql file
1
select * from census.newtable limit 1
2
​
3
--!wh-run
Copied!
would, upon execution using wh run, would be overwritten as:
1
select * from census.newtable limit 1
2
​
3
/* results: 2021-01-12 14:42:24.318297
4
--------------------------------------
5
   customer_id       date1 test_field
6
0            1  2019-10-01       None
7
*/
Copied!
Running SQL blocks within markdown files
The wh run command can also be used against files with the .md or .markdown extension, to enable more advanced Jupyter-notebook style behavior within your IDE.
Any block (```sql) containing --!wh-run will flag said block will:
1.
Flag this block for execution when wh run is called on this file.
2.
Upon execution, replace the line containing --!wh-run with a block of results.
This behavior is very similar to the execution within SQL files as shown above, but enables execution of SQL query blocks alongside context written in Markdown.
For instance, the following Markdown file
1
# My project
2
​
3
I've found that we've had some problems with this census table!
4
​
5
```sql
6
select * from census.newtable limit 1
7
​
8
--!wh-run
Copied!
1
would be overwritten upon execution of `wh run` as:
2
​
3
```text
4
# My project
5
​
6
I've found that we've had some problems with this census table!
7
​
8
```sql
9
select * from census.newtable limit 1
10
​
11
/* results: 2021-01-12 14:42:24.318297
12
--------------------------------------
13
   customer_id       date1 test_field
14
0            1  2019-10-01       None
15
*/
Copied!
1
For those familiar with Jupyter or R markdown notebooks, this pattern might feel somewhat foreign. Unlike with full-fledged programming languages, there is no need for logic to be transferred between cells in SQL, so we've made the conscious decision to simplify the usage pattern and supporting code by not building out support for execution of individual code blocks except for through explicit inclusion of the `--!wh-run` statement. This has the added benefit of being minimally destructive, only replacing the `--!wh-run` character sequence.
2
​
3
### Editor configuration
4
​
5
#### Vim
6
​
7
Add the following to your `.vimrc` file, and you can run `<Leader>wh` to execute whale files. `<Leader>` is generally `\` or `,`.
8
​
9
```text
10
nmap <Leader>wh :w<CR>:exec '!~/.whale/bin/whale run %'<CR>:e<CR>
Copied!
Or if installed via Homebrew:
1
nmap <Leader>wh :w<CR>:exec '!/usr/local/bin/wh run %'<CR>:e<CR>
Copied!
Vscode
TODO

Setup - Previous

Git setup

Next - Additional features

Query automation and alerting

Last modified 4mo ago

Copy link

Contents

Executing SQL files

Jinja templating

Saving results as comments

Running SQL blocks within markdown files