[5.1.0] - 2024年05月02日

Changed

• Attempting to load a database without providing all the custom classes persisted in it to your JSDB.open() call now throws an error instead of corrupting your database by falling back to using an untyped object.

• Above change means the custom object instantiation code in your tables is different. However, this is not a breaking change. Any databases created in the last two days since the release of JSDB 5.0.0 will automatically be updated to the next syntax as they are compacted on database open. (If you have compaction turned off, the new behaviour will only apply to newly-persisted objects.

Added

• JSDF version 2 to 3 migration script (i.e., JSDB version 2-4 to 5 migration script). For usage instructions, please see the readme.