Overview
| Artifact ID: | 76003ed8be6bbf2de50e6b4e34ecbaf9f9e2cbfb |
|---|---|
| Ticket: | d40c2b0eb6f90f9d2b94878780dee3b36f25d780
sqlite3_key_v2 and sqlite3_rekey_v2 ignore the zDbName parameter |
| User & Date: | mistachkin 2018-05-29 22:57:05 |
Changes
- icomment:
Thanks for the report. It appears that this behavior was by design when these APIs were originally added to System.Data.SQLite. Changing it now would break backward compatibility. Originally the legacy CrypoAPI support functions were designed for internal communication between the managed components of System.Data.SQLite and the SQLite interop assembly. They were not intended to be a public interface. Finally, the legacy CryptoAPI support is no longer officially supported. For the time being, it is still being included in the release builds; however, that will change at some point.
- login: "mistachkin"
- mimetype: "text/x-fossil-plain"
- priority changed to: "Medium"
- resolution changed to: "Not_Backwards_Compatible"
- status changed to: "Closed"
- subsystem changed to: "Legacy_CryptoAPI"
- type changed to: "Feature_Request"