There are legitimate uses for such things. We are currently implementing a processing rules configurator UI and backend that must ultimately be executed in sql

There are legitimate uses for such things. We are currently implementing a processing rules configurator UI and backend that must ultimately be executed in sql. It must support arbitrary nested boolean logic and comparison expressions. Last time we did this we ended up developing a custom data structure for the front-end and a custom printer for the sql output. This is a standardized version of solving just that problem. My question is if not a solution like this how then SHOULD I be implementing communication of such rules from the frontend to the backend?