Skip to content

Updating Libsql to latest version #262

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 8, 2025
Merged

Conversation

levydsa
Copy link
Contributor

@levydsa levydsa commented Apr 28, 2025

No description provided.

@ospfranco
Copy link
Contributor

Is this correct @haaawk ? It seems to reduce the file sizes quite a bit?

@haaawk
Copy link
Contributor

haaawk commented May 5, 2025

If @levydsa says so than probably yes.

@ospfranco
Copy link
Contributor

The api seems to have changed @levydsa you will need to update the source files for the bindings. What does the offline flag do? The docs will also need an update

@ospfranco
Copy link
Contributor

Whelp... I got no responses. Going to merge this and do a release... the question remains open what does the offline flag do and if the bindings need an update to expose this flag to the JS api

@ospfranco ospfranco merged commit 1a3098f into OP-Engineering:main May 8, 2025
8 checks passed
@twelvearrays
Copy link

The offline flag does need to be exposed on the JS api side, so that we can do offline line writes and then later have the offline writes sync back via openSync().

https://turso.tech/blog/introducing-offline-writes-for-turso

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants