It would replace libpg_query entirely.

I am currently contributing a bit tohttps://squawkhq.com because the parser there is quite advanced compared to any other attempt I have seen so far.

I am also aware of thesqruff parser (https://github.com/quarylabs/sqruff/blob/main/crates/lib-dialects/src/postgres.rs), but I don't know how it compares to squawk.

The configuration could take inspiration fromhttps://github.com/UniqueVision/plpgsql-lsp?tab=readme-ov-file#query-parameters

{  "plpgsqlLanguageServer.queryParameterPattern": ":[A-Za-z_][A-Za-z0-9_]*"}

hey! i think we can now start to work in this. our approach now is to

• use a custom lexer to not already break there (done),
• bring a custom binding for libpg_query in (use the custom libpg_query binding #453),
• build a preprocessor for libpg_query that replaces the parameters based on a config.

I think this is the easiest and most robust approach. the important part was the custom lexer that supports all kind of parameters.

Awesome!