ORMs and SQL at least have the same goal which is to join datasets and perform operations on them.
SaaS platforms build _filter languages_ that are (sometimes vaguely) inspired by SQL. I really wish there was a standard among filter languages that was optimized for interactive search. Interactive search is different from application search because in interactive search you don't know what fields there are so you are mostly counting on substring matches. But you still want to be able to include multiple substring matches (AND) and exclude things as you find them that aren't what you're looking for (AND NOT).
I think Google's search language is one of the best filter languages out there in terms of simplicity/effectiveness. Splunk's language is good as well (but maybe they're just making up for it in good typeahead support).
I'd like a standard for Google's search language with implementations for in-memory filtering in every major programming language and implementations for generating SQL from the filter for every major programming language.
Until this happens there's not really much hope for standardizing on filters across applications.
> Splunk's language is good as well (but maybe they're just making up for it in good typeahead support).
Not just typeahead. A lot of Splunk's power comes from data transformations and filters.
get_logs
| apply_transform
| merge with other logs (which can also be log|transform|filter|transform)
| apply more transforms
| filter
| expose as a specific structure (that is, transform)
| filter more
This would be anywhere from pain to impossible with SQL.
SaaS platforms build _filter languages_ that are (sometimes vaguely) inspired by SQL. I really wish there was a standard among filter languages that was optimized for interactive search. Interactive search is different from application search because in interactive search you don't know what fields there are so you are mostly counting on substring matches. But you still want to be able to include multiple substring matches (AND) and exclude things as you find them that aren't what you're looking for (AND NOT).
I think Google's search language is one of the best filter languages out there in terms of simplicity/effectiveness. Splunk's language is good as well (but maybe they're just making up for it in good typeahead support).
I'd like a standard for Google's search language with implementations for in-memory filtering in every major programming language and implementations for generating SQL from the filter for every major programming language.
Until this happens there's not really much hope for standardizing on filters across applications.