![]() Upgrade to SQLite3 Multiple Ciphers version 1.3.8 (SQLite version 3.38.0).Upgrade to SQLite3 Multiple Ciphers version 1.3.9 (SQLite version 3.38.1).Upgrade to SQLite3 Multiple Ciphers version 1.3.10 (SQLite version 3.38.2).Upgrade to SQLite3 Multiple Ciphers version 1.4.2 (SQLite version 3.38.3).Upgrade to SQLite3 Multiple Ciphers version 1.4.3 (SQLite version 3.38.5).Upgrade to SQLite3 Multiple Ciphers version 1.4.6 (SQLite version 3.39.1).Upgrade to SQLite3 Multiple Ciphers version 1.5.3 (SQLite version 3.39.3).Upgrade to SQLite3 Multiple Ciphers version 1.5.4 (SQLite version 3.40.0).Added method wxSQLite3Database::IsInterrupted.Enhanced method wxSQLite3Database::Open allowing to set the VFS to be used.Upgrade to SQLite3 Multiple Ciphers version 1.6.0 (SQLite version 3.41.0).Upgrade to SQLite3 Multiple Ciphers version 1.6.1 (SQLite version 3.41.1).Upgrade to SQLite3 Multiple Ciphers version 1.6.3 (SQLite version 3.42.0).Upgrade to SQLite3 Multiple Ciphers version 1.6.5 (SQLite version 3.43.1).Upgrade to SQLite3 Multiple Ciphers version 1.7.0 (SQLite version 3.43.1).Starting with the release of wxSQLite3 4.6.0 this new implementation is used. Since August 2020 a new implementation of an encryption extension, capable of supporting SQLite version 3.32.0 and later, is available as a separate project, SQLite3 Multiple Ciphers. As a consequence, updating the wxSQLite3 encryption extension to support SQLite version 3.32.0 and later was no longer possible. They were introduced on Feb 7, 2020: "Simplify the code by removing the unsupported and undocumented SQLITE_HAS_CODEC compile-time option". With the release of SQLite version 3.32.0 on critical changes to the public SQLite code finally took officially effect, although they weren't officially announced. AES 256 Bit CBC - SHA1/SHA256/SHA512 HMAC ( SQLCipher versions 1 - 4).ChaCha20 - Poly1305 HMAC ( sqleet) ( default).Starting with versionĤ.0.0 the encryption extension allows to select the cipher scheme at runtime.Ĭurrently the following encryption schemes are supported: The decision whether to use 128 bit orĢ56 bit AES encryption had to be made at compile time. Since version 1.7.0 wxSQLite3 includes a key-based SQLite3 encryptionĮxtension using AES encryption. ![]() Tools are used to modify the database contents, since not all of these Special care has to be taken if external administration In ANSI builds theĬurrent locale conversion object (wxConvCurrent) is used for conversion Works best for the Unicode builds of wxWidgets. Provide automatic conversion between wxStrings and UTF-8 strings. Since SQLite stores strings in UTF-8 encoding, the wxSQLite3 methods Supported, like for example the creation of user defined scalar or WxSQLite3 does not try to hide the underlying database, in contraryĪlmost all special features of the current SQLite3 version are WxSQLite3 is a C++ wrapper around the public domain SQLite 3.x databaseĪnd is specifically designed for use in programs based on the wxWidgets WxSQLite3 - a lightweight wrapper for SQLite
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |