electric
electric copied to clipboard
Sync little subsets of your Postgres data into local apps and services.
We are doing some tests with large quantities of data (10000-15000 new rows) on a foreign key related table (so compensations messages are sent). What we've encountered is that sometimes...
This an example of a y-provider based on Electric. The code is based on [y-webscocket](https://github.com/yjs/y-websocket/) and the [yjs-demos/codemirror.next](https://github.com/yjs/y-codemirror.next/blob/main/demo/codemirror.js) - [x] Awareness and broadcast across tabs - [x] IDB persistence -...
We missed adding these back with the new repo.
feat(sync-service): Streaming the response to the client without waiting for the snapshot to finish
Previously shapes with one million rows or more (170MB+) would timeout waiting for the snapshot to be created. Now the snapshot is streamed from the database into storage while simultaneously...
The Typescript `ShapeStream` class is responsible for reading the Shape Log from the Electric server and feeding it to other code that'd like to do something with the stream e.g....
This PR addresses https://github.com/electric-sql/electric/issues/1449 as it adds support for qualified schema and table names. To this end, i modified `validate_table` to parse (quoted) schema and table names.
See the discussion in https://github.com/electric-sql/electric-next/issues/173
 This picture shows the max number of concurrent initial syncs per shape size. The takeaway is that when shape is large enough, we can't handle the next request because...
This involves at least two things: 1. Electric should be able to start streaming using an older timeline, then switch to the current one 2. Electric should identify transactions that...