It happens sometimes that the delimiter (e.g. " ) is skipped, messing up the csv.

See attached files.
reproduce-bug.zip

@shakty Is there a way to retrieve the JSON data from the NDDB.db() object? This is not a deal breaker but I'm assuming this data is stored in memory when the NDDB object is created and I'd prefer to access it from memory versus reading the source json file. Again this is not a deal breaker but a nice to have for efficiency in my case. Please let me know if that is possible.

Thanks for your help so far!! Really appreciate it!

@shakty I'm seeing the following and I was wondering if this is normal. Concerned about security here if there are perhaps alternate libraries that can be used to avoid vulernabilities. Seems like it's a NDDB dependency to use uglify?

uglify-js <=2.5.0
Severity: critical
Incorrect Handling of Non-Boolean Comparisons During Minification in uglify-js - GHSA-34r7-q49f-h37c
Regular Expression Denial of Service in uglify-js - GHSA-c9f4-xj24-8jqx
fix available via npm audit fix --force
Will install [email protected], which is a breaking change
node_modules/uglify-js
smoosh >=0.4.0
Depends on vulnerable versions of uglify-js
node_modules/smoosh
JSUS >=0.6.3
Depends on vulnerable versions of smoosh
node_modules/JSUS
NDDB >=0.4.3
Depends on vulnerable versions of JSUS
Depends on vulnerable versions of smoosh
node_modules/NDDB
shelf.js >=0.3.7
Depends on vulnerable versions of smoosh
node_modules/shelf.js

5 critical severity vulnerabilities

When you register a new operator on a NDDB, and then you breed it, the breeded NDDB doesn't have the registered operator.

At the moment it waits until the first item is inserted, but this causes confusion.

It could just one..

If, in nodeGame, I do

node.game.memory.add({player: node.player.id, stage: node.player.stage, data: { "foo": null }});
node.game.memory.save("data.json");

I get

​{
"player": "681934395222262",
"stage": {
"stage": 2,
"step": 1,
"round": 1
},
"data": {
"foo": "!?_null"
},
"timestamp": 1516569132070
}​

where instead I would have expected something like

​{
"player": "681934395222262",
"stage": {
"stage": 2,
"step": 1,
"round": 1
},
"data": {
"foo": null
},
"timestamp": 1516569132070
}​

It probably should not, or it should be an option. It is creating a new NDDB, but it is not expected that the insert handler is re-executed.

It would be great to have the SQL Like Operator.

Hi, I need some help since the documentation doesn't seem to mention this. How does one edit/update a value with the database?
Super confused and currently super critical for me to continue working with this library, please let me know, thanks!

I've tried intelisense but there's no suggestion in VSCODE, tried to look at the source code as well but couldn't search to find an update function.

An option to make something like NDDB.selectAll('test', '==') that would go through all the dimensions of the db, and check if it matches with the value in agreement with the operator.