Password-protected databases no longer work with 1.113, no rollback possible
Did a Nuget update to system.Data.Sqlite 126.96.36.199 today, and noticed that the ChangePassword method of ConnectionString is no longer supported (and that password-protected databases no longer open). Unfortunately, Nuget.org no longer offers a rollback to 1.0.112, so I had to do a source code rollback of my project to return to a functional build. Is there a way to get ChangePassword support back? Why was it dropped? Thanks, -Pete
(2.1) By Ulrich Telle (utelle) on 2020-06-02 20:58:49 edited from 2.0 in reply to 1.0 [link] [source]
DRH and the SQLite developer team decided in February to remove the undocumented and officially unsupported
SQLITE_HAS_CODEC feature (see DRH's response to a similar question a few days ago). SQLite version 3.32.x was the first released version affected by this change.
System.Data.SQLite 188.8.131.52 is based on SQLite version 3.32.1, and is therefore also affected.
Taking into account that the
SQLITE_HAS_CODEC feature was around in the SQLite code base for about 15 years or so, it was a bit unfortunate that its removal was not even mentioned in the release notes. However, for undocumented features one has to live with such decisions, unfortunately.
Ugh. I'm currently shipping a consumer solution based on the Password facility that was built into SQLite until the February build. I'm not sure I entirely follow the implications here, but it does sound like implementing any sort of compatible scheme with existing customer databases is likely going to be quite the project if this feature is removed.
Any chance of restoring the Nuget System.Data.SQLite 1.0.112 package on nuget.org to make rolling back/installing compatible versions with the Password facility possible? (As is, there's a fair amount of surgery/tricky manual version component installs required to spin up a System.Data.Sqlite-based Visual Studio solution targeting databases which use the legacy Password encoding.). It would definitely be a big help if there were a way to checkpoint our projects back to the last supported version.
Yes, same problem here. I'm in the middle of my beta test and didn't see this coming. Rolling out an unencrypted db for now is not a problem, but I'd love to have a solution to this
Rolling out an unencrypted db for now is not a problem, but I'd love to have a solution to this.
Richard (the project lead), posted that it was never a documented or supported feature. The solution is to license SEE.
I got SQLiteCrypt to work. Perfect for my purpose and it doesn't cost like $2000. Also got rid of the Nuget package, cleans things up nicely
(9) By Nando (nandostyle) on 2020-07-23 02:08:20 in reply to 6 [link] [source]
But, it is not open source. Or is it? Trust no one!
I tried to retrieve older version by modify the link from new one For example:
Modify this link
And VOILA !!!
Disclaimer : -Above method is work per 2020/07/20 -Not all version worked
To install System.Data.SQLite.Core 184.108.40.206 from the Package Manager Console within Visual Studio, run the following command:
Install-Package System.Data.SQLite.Core -Version 220.127.116.11 -Source http://nuget.yuanbei.biz/nuget/Default
(8) By Nando (nandostyle) on 2020-07-23 02:05:22 in reply to 7 [link] [source]
You beat me to this comment. This will help many! It was hard to find how to install an earlier version.