Skip to content

Releases: Willena/sqlite-jdbc-crypt

SQLite-jdbc-3.38.0

24 Apr 09:56
Compare
Choose a tag to compare

Full Changelog: 3.37.2...3.38.0

Note: freebsd binaries (x86, x64, arm64, armv7) are missing in this particular version

SQLite-jdbc-3.37.2

15 Jan 23:33
Compare
Choose a tag to compare

Full Changelog: 3.37.1...3.37.2

Note: freebsd binaries (x86, x64, arm64, armv7) are missing in this particular version

SQLite-jdbc-3.37.1

15 Jan 23:17
Compare
Choose a tag to compare

Full Changelog: 3.37.0...3.37.1

Note: freebsd binaries (x86, x64, arm64, armv7) are missing in this particular version

SQLite-jdbc-3.37.0

15 Jan 22:55
Compare
Choose a tag to compare

Full Changelog: 3.36.0.1...3.37.0

Note: freebsd binaries (x86, x64, arm64, armv7) are missing in this particular version

SQLite-jdbc-3.36.0.1

15 Jan 22:10
Compare
Choose a tag to compare

What's Changed

Full Changelog: 3.36.0...3.36.0.1

Note: freebsd binaries (x86, x64, arm64, armv7) are missing in this particular version

SQLite-jdbc-3.36.0

04 Sep 23:30
Compare
Choose a tag to compare
  • Synced with Xerial repository
  • Updated to 3.36.0

SQLite-jdbc-3.35.5.3

06 Jun 11:11
Compare
Choose a tag to compare
Updated version to 3.35.5.3 + Force snapshot on develop branch

SQLite-jdbc-3.35.5.2

24 May 20:40
Compare
Choose a tag to compare

Updated to SQLiteMC 1.3.2

Note from SQLiteMC maintainer:

⚠️ Important Information when operating SQLite in WAL journal mode ⚠️

To allow concurrent use of SQLite databases in WAL journal mode with legacy encryption implementations like System.Data.SQLite or SQLCipher a new WAL journal encryption implementation was introduced in SQLite Multiple Ciphers version 1.3.0.

Unfortunately, WAL journals left behind by versions <= 1.2.5 are not compatible with this new implementation. To be able to access WAL journals created by prior versions, the configuration parameter mc_legacy_wal was introduced. If the parameter is set to 1, then the prior WAL journal encryption mode is used. The default of this parameter can be set at compile time by setting the symbol SQLITE3MC_LEGACY_WAL accordingly, but the actual value can also be set at runtime using the pragma or the URI parameter mc_legacy_wal.

In principle, operating generally in WAL legacy mode is possible, but it is strongly recommended to use the WAL legacy mode only to recover WAL journals left behind by prior versions without data loss.

SQLite-jdbc-3.35.5.1

02 May 14:09
Compare
Choose a tag to compare

Updated to SQLiteMC 1.3.1 - SQLite 3.35.1

SQLite-jdbc-3.35.5

26 Apr 22:30
Compare
Choose a tag to compare
Merge branch 'develop'

# Conflicts:
#	VERSION
#	pom.xml