HN user

vbalegas

8 karma
Posts0
Comments9
View on HN
No posts found.

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 works for old clients.

You can learn more about our support for migrations here: https://electric-sql.com/docs/usage/data-modelling/migration...

Native clients will be coming a bit later.

You can use the shapes to control what data syncs to the device: https://electric-sql.com/docs/usage/data-access/shapes

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 permissions implementations. If you want to do row-based filtering based on user_id today, you can add a special column 'electric_user_id' to your table: https://electric-sql.com/docs/reference/roadmap#shapes

We plan to integrate Electric with popular web frameworks: https://electric-sql.com/docs/integrations/frontend. To integrate with Angular, the client should work out of the box. What you'd need is to provide is the code for reactivity, which should not be a lot. Reach out on Discord and we can have a chat about it.