sqlbind

I'm author of sqlbind[1] and since t-strings announce have been thinking really hard how to incorporate it. Like obvious cases `t"select * from table where id = {id}"` are tempting only at first glance. But simple queries could be written by other means. Dynamic ones where you should drop part of query by some condition is a real problem. Your solution is impressive. It would be quite hard to support crazy sql extensions, for example for ClickHouse but as a concept it really ingenious. [1]: https://github.com/baverman/sqlbind

It seems article shows the opposite argument. SQL builders are useful not to write fragile raw sql ridden with noisy filter patterns with repeated numbered placeholders which could be easily broken on refactoring. Also it's impossible to compose queries with abstracted parts. Shameless plug: https://github.com/baverman/sqlbind

Static templates for SQL becomes a chore to express dynamic queries. A dynamic query depends from incoming request. For example search filters should add or delete conditional expressions for a query. I have a little research[1] on dynamic queries. [1]: https://github.com/baverman/sqlbind?tab=readme-ov-file#dynam...

Proposed safe(r) API via decorated methods: QParams = sqlbind.Dialect.some_dialect @QParams def make_my_query(value1: str, value2: int): return f'SELECT * FROM table WHERE field1 = {value1} AND field2 > {value2}' data = connection.execute(*make_my_query(foo, bar)) Obviously this wouldn't work as-is, QParams would need to be modified to support this. The decorator would wrap the method, sanitising the args before they're even passed to the wrapped function. Edit: actually, I might've misunderstood what sqlbind is doing internally, maybe this approach doesn't quite make sense Edit 2: Like so: https://github.com/baverman/sqlbind/issues/1