How Can i Consolidate Multiple PRQL Snippets into a Single File?

[ymolists]

Hello everyone,

I'm currently working on translating all my PRQL queries into JSON format and then parsing these JSON files. However, I've encountered an issue where this process results in small fragments of PRQL code being scattered across multiple .prql files within my directory.

Is there a way to consolidate many small snippets of PRQL code into the same file so that they can be easily referenced? Any guidance or suggestions on how to achieve this would be greatly appreciated!

Thank you!

[aljazerzen]

Yes. You can put multiple variable definitions into same .prql file:

# queries.prql

let a = (from x)

let b = (from y)

from z

When compiling them to SQL, you have to provide the "path" to the expression you want compiled:

# prqlc compile queries.prql - a
SELECT * FROM x

# prqlc compile queries.prql - b
SELECT * FROM y

# prqlc compile queries.prql - main
SELECT * FROM z

[ymolists]

Thank you so much for your help !

1. can i make it fail during parsing if the query is not valid ?
2. is it possible to show type information in the resulting output ? i am not really sure how i would see type information (like int, float) in the resulting json/yaml output

here is what i did .

prqlc parse --format json test.prql

error it here // make it fail

let a = (from x)

let b = (from y)

from z

[aljazerzen]

1. If you use compile command, it will fail if parsing was not successful.

2. You can look at the resulting status code of the process.

> prqlc compile valid.prql - main
SELECT
  *
FROM
  z

-- Generated by PRQL compiler version:0.13.3-13-g40bdca54 (https://prql-lang.org)
> echo $?   # print status code of last command (0 means success)
0

> prqlc compile invalid.prql - main
Error:
   ╭─[:4:19]
   │
 4 │ let b = (from y | asxasx)
   │                   ───┬──
   │                      ╰──── Unknown name `asxasx`
───╯

> echo $?   # print status code of last command (1 means error)
1

[ymolists]

Sorry for not bein clear in 2) . i meant to say output type information that can be used for type checking from the parse tree not just the ast tree. as in int, float, string etc .. ? is the compiler able to lift those types from the underlying query and out it as json ?

[aljazerzen]

Oh, the compiler does not produce much useful typing information yet. There is some, but I would not consider it stable enough to expose in a public API.