Garry Hill
Garry Hill
Fixes #1718
Alternative to the hybrid file + cubdb storage implementation. Currently implemented with both snapshots and log written to sqlite, but we could always go back to the hybrid model if...
When electric is included as a dependency then the configuration done in our `config/runtime.exs` is not used, and the application needs to set electric up itself. Because we've made every...
Currently we build a "canary" image `electricsql/electric:canary` off of `main`. Because the tag `electricsql/electric:canary` is not stable, if we ask someone to pull an image based off of main, we...
and tidy up telemetry config a little and make the call-home url configurable
Fixes #1719 - I think. Don't know if we've made other changes to the replication system since after 1719 but things seem robust against a storage reset. This pr does...
Currently we only support db-backed ecto.schemas, but we can leverage the type casting powers of ecto by supporting embedded schemas and mapping any data to ecto schema structs ```elixir defmodule...
Something like: ``` elixir {:ok, write_id} = Electric.Client.transaction_with_write_id(Repo, fn -> Repo.update(changeset) end) ``` (?) Write id implementation: - transaction xid - metadata column in table For the latter then we...
> With the through-the-DB write pattern, we can "standardise" a transactions: [[change, …], […]] payload format for handling locally made changes. The change message can be our existing message format....