LiteDB Versions Save

LiteDB - A .NET NoSQL Document Store in a single data file

v5.0.19

2 months ago

What's Changed

New Contributors

Full Changelog: https://github.com/mbdavid/LiteDB/compare/v5.0.18...v5.0.19

v5.0.18

2 months ago

What's New

  • Added "AutoRebuild" option in Connection String

In this version, the Rebuild command has been completely redesigned to be able to recover a full or partial database in case of data corruption. When detecting a structural error (known as the ENSURE exception) the data file will be modified to indicate that this file may be corrupt. When reopening the database, a rebuild process can be performed recovering as much data as possible. Use the "auto-rebuild=true" option in the connection string to activate this functionality. Possible errors found during the rebuild process will be stored in a new collection called "_rebuild_errors". A backup of the original file is created with the "-backup" suffix

What's Changed

New Contributors

Full Changelog: https://github.com/mbdavid/LiteDB/compare/v5.0.17...v5.0.18

v5.0.17

9 months ago

What's Changed

New Contributors

Full Changelog: https://github.com/mbdavid/LiteDB/compare/v5.0.16...v5.0.17

v5.0.16

1 year ago

What's Changed

New Contributors

Full Changelog: https://github.com/mbdavid/LiteDB/compare/v5.0.15...v5.0.16

v5.0.14

1 year ago
  • Fix PR #2227 (thanks to @rainman-306)

v5.0.13

1 year ago
  • Fix security vulnerability in deserialize bad json in .NET 4.5

v5.0.12

1 year ago
  • Made DiskWriterQueue more reliable so that it can handle multiple back calls better
  • Fix missing _type when serializing a covariant collection
  • Fix reload last index node after some page defrag
  • Replace ToUpper to ToUpperInvariant
  • Fix monitor transaction leaking
  • Fix minor bugs

v5.0.11

2 years ago

Bugfixes

  • #1275
  • #1772
  • #1956
  • #2021
  • #2023

v5.0.10

3 years ago

Bugfixes

  • Fix invalid multi-page CString reader
  • Fixed issue when checkpoint soft limit not applied for manual transaction

ENSURE in Release mode

  • This new 5.0.10 contains an adicional test layer called ENSURE used in all storage/cache layer. Until now, this tests was executed only in DEBUG mode but now we add into RELEASE mode too. If any ENSURE are violated a system exception will be throwed (prefix message "LiteDB ENSURE:"). This will better for detect and prevent data corruption database and much better diagnostics and bugfixes. Complex tests (like check if a byffer is empty) still run in DEBUG mode only to avoid performance down.