Parent and child using same db about nedb HOT 9 CLOSED

Hello,

This doesn't come as a surprise since nedb is not run in a separate process but instead in the same process as the node application. That means the persistence datafile can be written to by the two processes but an insert on the parent will not be reflected on the child's in-memory cache.

I don't think nedb should automatically be in a separate process though, since its goal is to be lightweight. That said, what we can do is a standalone application that uses nedb to provide a database accessible through HTTP.

I'm not sure I can to that in the near future since there are other priorities for nedb, but I don't think it would take too long so if you want to do it please tell me and when it's finished I'll link to it in nedb's readme.

from nedb.

PS: I was thinking about it again and in fact I don't think that building this cross-application version of nedb makes sense. If you need this, you probably want to use a large scale database such as MongoDB. The goal of nedb is to provide database functionality to small-scale, simple applications and that doesn't seem to be your case.

from nedb.

On the other hand you can setup db on the parent and just pass new entries from child via process.send(insert) and worker.on('message'). Not the prettiest way but still should do the trick.

from nedb.

You can certainly do it that way too but that's very custom so I wouldn't want to implement this in nedb. I'm not too sure how a simple application can need to share access to a common database with a child, are you sure mongodb is not the right solution for your needs ?

from nedb.

Application doesn't store a lot of entries in the db and while most of the heavy lifting is done on the forked child process data has to be accessed from the parent. With the nedb application can run in a smaller enviro without requirement for a large db setup.

from nedb.

I see. Since it's very specific, the best way to do it would be for you to manage cross process communication and have only one nedb running, in the child.

from nedb.

Just tested it and works pretty nice. By the way is nedb vulnerable to traditional SQL injection attacks?

from nedb.

No. The only thing that you could think of is putting arbitrary javascript code in a form. But since the serialization/deserialization doesn't use eval and new Function (only JSON), this code would never get executed.

from nedb.

Thanks Louis.

from nedb.