Adding OR logic forced us to confront why users preferred raw SQL

Re:Adding OR logic forced us to confront why users preferred... by prpl on Saturday September 13, 2025 @11:34PM (#45237205)

Salesforce’s SOQL, like was mentioned with Jira’s JQL, also handles this type of thing _okay_ without explicit joins.

I think “SQL is the interface” even for telemtry is the thing that truly makes sense, but it is messy with logs compared to splunk for example

[ Parent | on HN ]

Re:Adding OR logic forced us to confront why users preferred... by shakna on Sunday September 14, 2025 @12:38AM (#45237483)

SoQL's lack of joins and subqueries makes it a real pain in my life. `having` and `group by` are not enough when doing a lot of things - like confirming data migration of 40m objects.

Can't do a query builder in one step, or must write Apex.

[ Parent | on HN ]

Re:Adding OR logic forced us to confront why users preferred... by ankitnayan on Sunday September 14, 2025 @04:28AM (#45238406)

and here query builder helps by making it earier to do cross-signal joins and subqueries. I see that is upcoming in SigNoz https://signoz.io/blog/query-builder-v5/#what-we-couldnt-shi...

[ Parent | on HN ]