The main difference seems that nedb is in memory. With JSONLines you cannot mutate the original file. But we do know where in memory each row is. So my first step would be to figure out how to replace a row in the file.
Btw, Jacob recently added JSON lines capability to JSON3.jl.
2 Likes
Ah very cool. I’m using JSON3 now for parsing. I think the primary difference is that JSONLines is primarily out of memory while indexing the lines which allows for multicore filtering for example. But if you want to read the entire file it’s probably best to go with JSON3 directly.
1 Like