You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems libSQL doesn't sync on start even though readme says "Initial sync happens when you first connect". Agent says "connect never calls db.sync()".
@taronomy This should be fixed now with the PR #125 but I haven't done a release yet as I'm merging some other fixes, will let you know and close this when the next release comes out.
@taronomy On the second comment of yours about new Turso cloud compatibility: that invalid type: string "v1", expected u32 error is separate from the initial-sync fix in #125 and won't be resolved by it - it happens inside libSQL's own sync handshake, before any sync call, and affects databases created since Turso Cloud switched engines. libSQL's latest pre-release still carries the same handshake code, so a version bump is unlikely to help.
Since libSQL is winding down in favour of Turso's new turso library, I'm exploring building a new Ecto adapter built on that, I'll let you know. There are some other Elixir libs that use the new turso library, but not at the full Ecto adapter level.
Activity
taronomy commentedon Aug 6, 2026
The release of Turso on Turso Cloud made new DBs incompatible. (even though the DB is LibSQL, not Turso)
ocean commentedon Sep 17, 2026
Sorry for the delay @taronomy - having a look at this now.
ocean commentedon Sep 19, 2026
@taronomy This should be fixed now with the PR #125 but I haven't done a release yet as I'm merging some other fixes, will let you know and close this when the next release comes out.
ocean commentedon Sep 21, 2026
@taronomy On the second comment of yours about new Turso cloud compatibility: that
invalid type: string "v1", expected u32error is separate from the initial-sync fix in #125 and won't be resolved by it - it happens inside libSQL's own sync handshake, before any sync call, and affects databases created since Turso Cloud switched engines. libSQL's latest pre-release still carries the same handshake code, so a version bump is unlikely to help.Since libSQL is winding down in favour of Turso's new
tursolibrary, I'm exploring building a new Ecto adapter built on that, I'll let you know. There are some other Elixir libs that use the newtursolibrary, but not at the full Ecto adapter level.