Jon Gjengset

As an aside, `noria-server` probably won't be on crates.io until https://github.com/rust-lang/cargo/issues/1565 is solved (which may be a while).

@mjjansen - Push notifications (basically, pushing parts of the data-flow to the client) is something that's definitely on our radar, and was actually one of the motivations for using data-flow...

That crate didn't exist when we first started building Noria :) Combining efforts is probably not a bad idea though! (cc @ms705)

Hehe, yes, a Postgres adapter would be great, it just requires implementing the Postgres binary protocol in Rust similar to [`msql-srv`](https://github.com/jonhoo/msql-srv). That's the bulk of the work. Once that's in...

So, push notifications are tricky because they imply full materialization everywhere, which comes at a steep cost. There might be a good way to register interest in keys and *then*...

Hi! Jonathan's summary is essentially correct, though let me try to give a more direct answer to your question. The materialized views in Noria are not re-calculated in the same...

Hi! Noria does not have transactions in the traditional sense. Specifically, as the _client_ you cannot say "read this, write this, read this, write this" as an atomic unit. If...

Noria is also a research prototype, so we're not expecting anyone to pick it up and use it in production any time soon :) As for inefficiently supporting transactions, the...

For the e-mail queue, I think the equivalent encoding is to define a view that is "job" left joined with a "SELECT job, worker FROM claims ORDER BY id ASC...

Yup, Noria (at least in theory) could totally tell you when the results change. It's not something that's currently supported, but shouldn't be too hard to add. It certainly meshes...