Stop syncing everything

(sqlsync.dev)

Show context

matlin ◴[02 Apr 25 02:28 UTC] 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 #

1. nilamo ◴[02 Apr 25 03:39 UTC] No.43553449[source]▶

>>43553179 #

I heavily disagree with the notion that most developers would rather query with something that isn't SQL.

replies(2): >>43553533 #>>43555548 #

2. kreetx ◴[02 Apr 25 03:56 UTC] No.43553533[source]▶

>>43553449 (TP) #

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 #

3. blatantly ◴[02 Apr 25 06:57 UTC] No.43554292[source]▶

>>43553533 #

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.

4. robertlagrant ◴[02 Apr 25 11:22 UTC] No.43555548[source]▶

>>43553449 (TP) #

Probably the biggest upgrade SQL could have is putting the SELECT after the FROM, so autocomplete would work nicely.

5. ◴[02 Apr 25 23:08 UTC] No.43562839[source]▶

>>43553533 #

6. nilamo ◴[02 Apr 25 23:09 UTC] No.43562848[source]▶

>>43553533 #

Exactly. Hard to improve on something so great.

We love a

``` select {what} from {where} left join {where} on {how} where {why} ```

A simple query, concisely answering every relevant question, while hiding all of the details of how any of it works. Beautiful.

↑