Pipes
Pipes are the connection between transforms that make up a pipeline. The relation produced by a transform before the pipe is used as the input for the transform following the pipe. A pipe can be represented with either a line break or a pipe character (|
).
For example, here the filter
transform operates on the result of from employees
(which is just the employees
table), and the select
transform operates on the result of the filter
transform.
PRQL
from employees
filter department == "Product"
select {first_name, last_name}
SQL
SELECT
first_name,
last_name
FROM
employees
WHERE
department = 'Product'
In the place of a line break, it’s also possible to use the |
character to pipe results between transforms, such that this is equivalent:
PRQL
from employees | filter department == "Product" | select {first_name, last_name}
SQL
SELECT
first_name,
last_name
FROM
employees
WHERE
department = 'Product'
“C’est ne pas un pipe”
In almost all situations, a line break acts as a pipe. But there are a few cases where a line break doesn’t act as a pipe.
- before or after tuple items
- before or after list items
- before a new statement, which starts with
let
orfrom
(orfunc
) - within a line wrap
For example:
PRQL
[
{a=2} # No pipe from line break before & after this list item
]
derive {
c = 2 * a, # No pipe from line break before & after this tuple item
}
SQL
WITH table_0 AS (
SELECT
2 AS a
)
SELECT
a,
2 * a AS c
FROM
table_0
PRQL
let b =
\ 3 # No pipe from line break within this line wrap
# No pipe from line break before this `from` statement
from y
derive a = b
SQL
SELECT
*,
3 AS a
FROM
y
Inner Transforms
Parentheses are also used for transforms (such as group
and window
) that pass their result to an “inner transform”. The example below applies the aggregate
pipeline to each group of unique title
and country
values:
PRQL
from employees
group {title, country} (
aggregate {
average salary,
ct = count salary,
}
)
SQL
SELECT
title,
country,
AVG(salary),
COUNT(*) AS ct
FROM
employees
GROUP BY
title,
country