SQLitePCL support

[baaaaif]

I would like to use the current version of SQLite3MultipleCiphers within SQLitePCL.raw.
The releases maintained by Eric Sink are not really keeping up with those of SQLite3MultipleCiphers.
Are there any other options?
Something like the artifacts from https://github.com/utelle/SQLite3MultipleCiphers-cb or something like that?

[utelle]

I would like to use the current version of SQLite3MultipleCiphers within SQLitePCL.raw. The releases maintained by Eric Sink are not really keeping up with those of SQLite3MultipleCiphers.

I agree that it would be desirable if the project SQLitePCL.raw would publish releases more frequently. However, at least there is a prerelease available which is based on SQLite3MC 1.9.2 (released in December 2024) - see NuGet.org.

Currently I'm working on fixing some issues in SQLite3 Multiple Ciphers. The next release will probably take place within a week or so. Maybe Eric Sink can be convinced thereafter to make a new release of SQLitePCL.Raw based on the latest version.

Are there any other options? Something like the artifacts from https://github.com/utelle/SQLite3MultipleCiphers-cb or something like that?

SQLite3MultipleCiphers-cb is my playground to test compatibility with SQLitePCL.Raw. After the next release of SQLite3MC I will update this project to test the latest version.

Then there is SQLite3MultipleCiphers-NuGet, which depends on SQLite3MultipleCiphers-cb - also just used for testing purposes. However, the GitHub CI workflow creates an artifact that may be usable. Unfortunately, the last workflow run happened 4 months ago, so that the artifact has already expired. If you are interested in giving it a try, I can update this project, too, after the next release.

[baaaaif]

Thank you very much for this really helpful and detailed answer, I really appreciate it.
I would definitely like to try out the test version from the playground and will keep an eye on the workflow results

[utelle]

I would definitely like to try out the test version from the playground and will keep an eye on the workflow results

I made a release for SQLite3 Multiple Ciphers yesterday. Thereafter I updated SQLite3MultipleCiphers-cb, and the binaries were built successfully. However, the workflow failed, unfortunately - with the following error message:

Error: C:\Program Files\dotnet\sdk\9.0.200\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.EolTargetFrameworks.targets(38,5): error NETSDK1202: The workload 'net7.0-ios11.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/maui-support-policy for more information about the support policy.

I have to admit that the .Net world isn't really my world. That is, providing .Net support was only possible with the active support of Brice Lambson and Eric Sink. So, I will certainly try to solve the workflow issue, but I don't know whether I can manage it on my own.

[utelle]

There is a good chance that a new version of SQLitePCL.raw will be released in the near future - see Eric Sink's comment.

[utelle]

SQLitePCL.Raw 2.1.11 was released today, and supports SQLite3 Multiple Ciphers 2.1.0.

[baaaaif]

great! thank you for your efforts

[baaaaif]

A hint that might help someone who wants to migrate from, for example, SQLitePCLRaw.bundle_e_sqlcipher to SQLitePCLRaw.bundle_e_sqlite3mc:
sqlite3mc does not allow double quotes as identifiers by default (SQLITE_DQS=0).
After opening the connection, I was able to allow this again with this:
SQLitePCL.raw.sqlite3_db_config(connection.Handle, SQLitePCL.raw.SQLITE_DBCONFIG_DQS_DDL, 1, out int _);
SQLitePCL.raw.sqlite3_db_config(connection.Handle, SQLitePCL.raw.SQLITE_DBCONFIG_DQS_DML, 1, out int _);
(my connection is a Microsoft.Data.Sqlite.SqliteConnection)

https://www.sqlite.org/quirks.html#dblquote

[utelle]

Unfortunately, the encryption feature in SQLitePCL.Raw 2.1.11 will currently not work properly. The reason is a change in behaviour of SQLite itself and a flaw in Microsoft.Data.SQLite - see issue #197 for details.

The issue has to be fixed in Microsoft.Data.SQLite.

[baaaaif]

Workaround see comment #197 (comment)

[utelle]

Workaround see comment #197 (comment)

Yes, explicitly excuting the necessary pragmas without using URI parameters and the Password property works, of course. However, using URI parameters in conjunction with SQLite3 Multiple Ciphers is easier and avoids problems with the order of pragmas.

However, it would be the best solution, if the Microsoft.Data.SQLite developers adjust the code accordingly.