Stability and usage for a Rust/C/C++ project

[adamski]

I would like to know if this repo is suitable for usage directly from a Rust or C/C++ application?

[simolus3]

To make the logic contained in the core extension easy to use for our higher-level SDKs, all methods are supposed to be called through SQL functions on a SQLite database. So the idea is that you'd build the PowerSync core extension (either as a loadable shared library or statically with your application) and then either use sqlite_load_extension (for shared libraries) or powersync_init_static (for static libraries).

After loading the extension, you can start a sync operation through e.g. the powersync_operations vtab registered on open databases. This is possible with Rust or C/C++ applications too (and you wouldn't even have to use APIs from this repository, every generic SQLite library for those languages would work). That said, there is lot of additional logic implemented in our SDKs, such as:

1. Calling powersync_initialize() to setup the schema.
2. Connecting to the PowerSync service and handling sync lines (we're working on changes to move more logic related to this away from SDKs and into the core extension).
3. Watching the ps_crud table for pending uploads and forwarding them to a backend connector.

So, while it's possible to use PowerSync directly from a native application, we don't have a full SDK for that to help fill the gaps. I don't think we currently have plans for that either, but you're welcome to suggest that for our roadmap. If you're interested in using PowerSync without a full SDK, we can also provide some pointers on which functions to call / what to do.

[simolus3]

We have a Rust SDK with higher-level bindings around the core extension now. That would definitely be suitable for Rust applications, so I'll close this issue.

Using the core extension directly is possible if you really want to, but it would probably require a bit of reverse engineering of our SDKs to analyze how it's used. There are some docs here but we are treating this as an internal project.