←back to thread

656 points neilk | 1 comments | | HN request time: 0.228s | source
Show context
matlin ◴[] No.43553179[source]
My ideal version of this is simple: just define the queries you want (no matter how complex) and the you'll get exactly the data you need to fulfill those queries, no more, no less. And the cherry on top would be to have your queries update automatically with changes both locally and remote in close to real-time.

That's basically what we're doing with Triplit (https://triplit.dev), be it, not with SQL--which is a plus for most developers.

replies(2): >>43553449 #>>43554513 #
nilamo ◴[] No.43553449[source]
I heavily disagree with the notion that most developers would rather query with something that isn't SQL.
replies(2): >>43553533 #>>43555548 #
kreetx ◴[] No.43553533[source]
Funny, as Triplit front page shows a query much like SQL:

  const deliveredMessagesQuery = client
    .query("messages")
    .Where("conversationId", "=", convoId)
    .Order("created_at", "DESC")
replies(3): >>43554292 #>>43562839 #>>43562848 #
1. blatantly ◴[] No.43554292[source]
Well yeah choosing what to query, a filter and an order is at the heart of all query-like things. Buy SQL specifically is a text language not a fluent api.