Util.deepCopy() question about jsondb-core HOT 2 OPEN

Hi Joel,

1. Deep copying was done so that the objects in memory would be disconnected from the objects returned by the various query method.
2. Not doing deep copy has one side effect, once you have queried and obtained object(s) from the JsonDB you can then change the contents of that object and those changes would also be done in the JsonDB memory, this would not be issue normally, however, it might cause subtle bugs especially in case of the update methods. You might end up assuming that I have changed the object and it is all done however the change will not be written to the files. This would mean data in cache is out of sync with data in the files. However, if you continue to invoke the update methods without fail you can choose not to do deep copy and it should all work fine.
3. Data files can be loaded in 2 ways. a) at the time of constructor invocation everything in data folder is loaded up front. b) you can invoke reload() method to load a particular collection again on demand. You can also register for event listners (though they don't work on mac) and reload based on events received when underlying data files change

Thanks

from jsondb-core.

I do not plan to change this behaviour at the moment. In future if time permits i can try and make it configurable, until then i am going to mark it wont fix

from jsondb-core.