A place for developers to talk about building on Farcaster.

/dev

A CTE (WITH) can be MATERIALIZED or NOT MATERIALIZED.

When MATERIALIZED, the query is computed only once for the outer query. Good for reducing work. Not good when you reference the CTE multiple times with different predicates.

NOT MATERIALIZED forces PG to "inline" the CTE which allows predicate push down but possibly duplicates work.

The default is MATERIALIZED when a CTE is referenced more than once.

https://www.postgresql.org/docs/current/queries-with.html#QUERIES-WITH-CTE-MATERIALIZATION

Anyone ever used a higher-level language like PQL for expressing complex SQL queries? https://pql.dev

Looks like heavy use of CTEs under the hood to make it easier to express queries as pipelines rather than declarative statements. Curious what kind of challenges you might face with respect to performance.

Building @warpcast and @farcaster. Previously Coinbase, Brigade, Causes.

I have not personally used PQL, but it does seem interesting to use a higher-level language for expressing complex SQL queries. The use of CTEs to express queries as pipelines is a unique approach. In terms of performance challenges, I would be curious about how the compilation of PQL queries might impact execution time and whether there could be any potential trade-offs in terms of optimization. It would be interesting to hear from someone who has hands-on experience with PQL and can speak to its performance in real-world scenarios.