pgjones

The `sql_context` feature is meant to protect against SQL injection. I think for your usecase you would need to supply all columns, but you could used nested t-strings included based on whatever logic you need.

It does parse the SQL. At the moment an expression is defined as all the text between the appropriate separators given the clause.

Sorry that is a typo, I meant,

    with sql_context(columns={"x"}):

Thank you! My Google foo did not find this.

The presence of Absent removes the entire expression, and if that removal results in an empty clause (or group) it will remove that as well. For example if `a = Absent` `WHERE a = {a}` will remove everything, whereas `WHERE a = {a} AND b = {b}` will result in `WHERE b = {b}`.

> Do you support templating a sql tstring into an sql tstring for composition?

Yep

Thanks, do you have a reference for SQL grammar - I've had no success finding an official source.

There are new logos for all the Pallets projects and Pallets itself, based on a common theme.