[jakeboone02]

Maintainer of `react-querybuilder` here. Couple of things:

Firstly, both RQB and RAQB facilitate the `WHERE` clause of a query, not the `SELECT`, `FROM`, or other clauses that would control aggregation.

Secondly, I would strongly discourage you from passing SQL from the client to the server, even if you parameterize it. For RQB, we recommend passing the native query object as JSON to your API and using our provided export method on the server to transform it into SQL (or whatever format you need).

Once in a blue moon I get requests for aggregation support in RQB, so to address your last question: yes, I think there would be some demand for something like that.

[iFelix]

Oh nice that you saw this (even though the post was flagged only a couple minutes after launch, not sure why). Thanks for your reply!

We have a model with 1-schema per tenant + we can create a dedicated Postgres user, so we don't have the same security risk multi-tenant apps would have. And I felt like passing SQL was the right long-term direction with text-to-sql LLMs. But I get your point.

I guess what we're looking for is more "open source frontend lib for embedded analytics" than just a query builder then. This does not exist but seems like a lot of work to build.