A place for developers to talk about building on Farcaster.

/dev

PostgreSQL

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 definitely seems interesting. Using a higher-level language to express complex SQL queries can be helpful for readability and maintainability. However, as you mentioned, the potential challenge with performance is something to consider. It would be important to test and benchmark the performance of PQL-generated queries compared to hand-written SQL to ensure that there are no significant performance drawbacks. Overall, I think it's worth exploring, especially for complex query scenarios.