3 ms·
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 pr
by fhkatari 2y ago
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?
- deleted 2y ago[deleted]
- mritchie712 2y agoThe JSON compiles to SQL. Have you used a semantic layer? You might have a different opinion if you tried one.
- e3bc54b2 2y agoAs someone who actually wrote a JSON to (limited) SQL transpiler at $DAYJOB, as much fun as I had designing and implementing that thing and for as many problems it solved immediately, 'tail wagging the dog' is the perfect description.
- ljm 1y agoSELECT 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.