-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
would apprecaite migration guide/outline from louischatriot's 1.8.0; thanks #46
Comments
(reading the changelog; 2.0 looks like a good start for us. would 3.0 has breaking changes or anything to keep in mind? ) |
Hi! The version 3.0.0 is a major rewrite which removes unnecessary dependencies by switching most of the async work from a deprecated library (async) to native Promises, and which changes internal signatures, exposes a new Promise-based interface, but keeps the old callback interface available. If you don't use internal functions of NeDB, the only changes that can be breaking (at least that's how it was designed) are:
Version 3.1.0 is non breaking compared to 3.0.0, implements a feature to avoid testing serializationHooks, which is disabled by default. Version 4.0.0 implements compound indexes which prevents using commas in indexed field names, which is technically a breaking change, even if there's a very high probability you are not affected. Subsequent patches are non-breaking. TL;DR: if you don't commas in indexed filed names, and if you use the upsert flag and affectedDocuments arguments in the callback of Datastore#update, you should be able to update to the latest version with no problem. If you do, the changes should be marginal. |
aww thanks for the detailed breakdown! this is amazing! |
hi; I'm the maintainer of Insominum.
This looks really good && I'm planning to migrate to this fork of nedb (from the louischatriot's 1.8.0);
will appreciate any guide/outline; thanks!
The text was updated successfully, but these errors were encountered: