Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What's the advantage of this over triggers in a relational database? Or even notify/listen in PostgreSQL? (assuming these triggers are connected to the API, of course).

I guess it's probably a matter of scale, but I really don't know.



It runs fully on the client and is offline first. A listener to PostgreSQL will not work when the device goes offline.


Fair enough, so what about triggers on a sqlite db on the client?


There is a big difference between having a changestream of writes to the database, and observing results of multiple queries.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: