db_watch
rethinkdb_rebirth
Our great sponsors
| db_watch | rethinkdb_rebirth | |
|---|---|---|
| 1 | 1 | |
| 0 | 1,016 | |
| - | - | |
| 0.0 | 0.0 | |
| about 3 years ago | about 5 years ago | |
| JavaScript | C++ | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
db_watch
-
Ask HN: Is there a way to subscribe to an SQL query for changes?
It's certainly not production situation, but I quickly made this [1] a while back to help with "watching" certain queries for debugging. It uses a polling approach.
[1] https://github.com/grouparoo/db_watch
rethinkdb_rebirth
-
Ask HN: Is there a way to subscribe to an SQL query for changes?
I know [RethinkDB][1] used to do this with their SQL-like ReQL language, but I looked around a bit and can't find much else about it - and I would have thought it would be more common.
If we think about modern frontends using SQL-based backends, essentially every time we render, its ultimately the result of a tree of SQL queries (queries depend on results of other queries) running in the backend. Our frontend app state is just a tree of materialized views of our database which depend on each other. We've got a bunch of state management libraries that deal with trees but they don't fit so well with relational/graph-like data.
I came across a Postgres proposal for [Incremental View Maintenance][2] which generates a diff against an existing query with the purpose of updating a materialized view. Oracle also has [`FAST REFRESH`](https://docs.oracle.com/database/121/DWHSG/refresh.htm#DWHSG8361) for materialized views.
I guess it's relatively easy to do until you start needing joins or traversing graphs/hierarchies - which is why its maybe avoided.
[1]: https://github.com/rethinkdb/rethinkdb_rebirth
What are some alternatives?
integrate - Core IntegrateDB source code repository.
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
pg-live-select - Live Updating PostgreSQL SELECT statements
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
flow - 🌊 Continuously synchronize the systems where your data lives, to the systems where you _want_ it to live, with Estuary Flow. 🌊
cainophile
timely-dataflow - A modular implementation of timely dataflow in Rust
PipelineDB - High-performance time-series aggregation for PostgreSQL
noria - Fast web applications through dynamic, partially-stateful dataflow