I've implemented the serialize method on SqliteConnection so that it returns an SqliteOwnedBuf. I'm still unwrapping some type conversions, I'll fix those in a follow-up change.

It would be cool to have a single serialize function on SqliteConnection which could return both the default and the nocopy buffers but I still have to figure out how to achieve the latter.

Update: I've moved serialize() and deserialize() on the worker thread but I have little knowledge of the codebase so feel free to point me in the right direction.

I had to introduce two new Command enumerations Serialize + Deserialize so that they can be used and passed in the worker tx channel.

serialize() probably requires more work, as @abonander pointed out

it may have to wait for concurrent write transactions from other connections to complete

plus, I've implemented Send + Sync for SqliteOwnedBuf just to silence the compiler complaints because NonNull<u8> is not thread-safe ofc.

I've also removed the NOCOPY implementation until we figure out how to handle that.

@mattrighetti on further review, there were a lot of things I wanted to change and it would have been unwieldy to do it all in review comments. I took the liberty of pushing a commit with the changes:

• expanded docs better matching the style of the rest of the project
• better error handling
• integration tests

Take a look and let me know what you think.

lgtm!

Not 100% convinced about the serialize(Option<&str>) but I guess it makes sense for this first iteration.

In the future we could introduce a new function serialize_schema(&str) where we explicitly ask for a schema while keeping serialize() as "main" schema serialization.