Releases: litedb-org/LiteDB
Releases · litedb-org/LiteDB
v5.0.16
What's Changed
- use only mutex for Shared engine open and close synchronization and remove locks by @dev-joshi in #2293
- Fix Min(Func<T,TResult>) handling by @gcrossland-cosworth in #2287
- Change return type of ILiteRepository.Insert to match ILiteDatabase.Insert by @InvisiblePhil in #2260
- Fixed typo by @iArmanKarimi in #2267
- try fix SqlLike by @pjy612 in #2235
New Contributors
- @dev-joshi made their first contribution in #2293
- @gcrossland-cosworth made their first contribution in #2287
- @InvisiblePhil made their first contribution in #2260
- @iArmanKarimi made their first contribution in #2267
- @pjy612 made their first contribution in #2235
Full Changelog: v5.0.15...v5.0.16
v5.0.15
v5.0.14
v5.0.13
v5.0.12
- 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
v5.0.10
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.
v5.0.9
Changes
- The
LiteDatabasector that takes aStreamfor its data storage now takes anotherStreamas log storage. LiteDB can now be used with custom storage solutions (as long as it implementsStream). - Custom serializers and deserializers can now be used even with basic BSON types. This is useful if you don't want to lose precision when storing
DateTime.
Bug fixes
v5.0.8
v5.0.7
New
- Maximum index key length increased to 1023 bytes
Upgradeoption inConnectionStringis now aboolagain (DataOnlyno longer needed because index key length was increased)- Id field in resolved includes are now stored with
$idkey (instead of_id)