vbalegas

5 ms·

1.
by vbalegas 3y ago
Awesome! Will check it out
2.
by vbalegas 3y ago
;)
3.
by vbalegas 3y ago
That's a great reference. Thank you for sharing.
4.
by vbalegas 3y ago
Thank you for playing with our demos and finding this issue! We'd welcome very much if you could reproduce the steps and report an issue: GH: https://github.com/electric-sql/electric/issues Discord: https:&#
5.
by vbalegas 3y ago
yes, ElectricSQL works for webapps with nodejs: https://electric-sql.com/docs/integrations/drivers/server/no...
6.
by vbalegas 3y ago
Apps with large dataset have their own characteristics: they are more tolerant to slower initial sync. We can resume replication at point-in-time, so even if a shape takes long to load, we can resume replication at the point we started sync
7.
by vbalegas 3y ago
It works similarly: migrations flow as part of the replication stream and clients apply them immediately, so that new data fits the local schema. New columns and etc might not immediately be exposed to the client app, but everything will wo
8.
by vbalegas 3y ago
You definitely can do row-level filtering (and a lot more) using DDLX[1], an extension we made to Postgres language that allows expressing flexible permission rules in a data-centric way. [1] https://electric-sql.com/docs&#x
9.
by vbalegas 3y ago
Valter from Electric here, Handling encryption/decryption of user data is one of our priorities. We're thinking along the lines of adding hooks for transforming data as you're seeing it. We're getting there on permission