Allow opening sqllite from bytestring via sqllite3_deserialize directive about direct-sqlite

[jchia]

sqlite3_deserialize() looks complicated. Any idea how to implement it properly in direct-sqlite? What are some use cases? From the documentation, I'm also not sure who owns pData after the call to sqlite3_deserialize().

Design proposal/discussion or PR welcome.

[meghfossa]

I can add some use cases here:

When working within (non-standard filesystem) - S3, tarball, zip, etc - We usually retrieve byte string of SQLite file. We are interested in working with this.
Right now, the workaround is: to persist this SQLite file in some temp file, do necessary operations and remove temp file.

[jchia]

For this use case, I don't understand why sqlite3_deserialize() even requires an existing database connection to disconnect first. Whoever implements sqlite3_deserialize() in direct-sqlite would have to understand what it really does. The documentation page is rather unclear. E.g. it talks about "serialization buffer" exactly once without explaining what it is or perhaps which variable it refers to.

[jchia]

PR welcome, possibly preceded by design/interface discussion.