You move all the tools to debug and inspect slow queries, in a completely unsupported JSON environment, with prompts not to make up column names. And this is progress?
SELECT email FROM users WHERE deleted_at IS NOT NULL OR status = 'active'
seems more semantic to me at first glance than piping this into a JSON->SQL library {
"_select": "email",
"_table": "users",
"_where": {
"deleted_at": { "_is": { "_not": SQL_NULL_VALUE } },
"_or": [
{ "status": "inactive" },
]
}
}
which is usually how these things end up looking.