Why no read-only DB open from other process?

[isbm]

Hi!
I am wondering why I cannot open a database from another process for read-only purposes. 😢 Currently it explicitly flock's the database and checks if it can do it again. But what if there would be a switch that errors all inserts/deletes/updates, but leaves working only reading methods?

This limitation pushes to reinvent a wheel with IPC so then the other programs has to communicate with the main thread of the locking app. I am still failing to understand what's wrong to just open the database and just read it?

Currently I have to copy the entire database to read it "offline" and then delete it, once I've done. 😢

[IGN-Styly]

in the same program you can clone it.

[isbm]

in the same program you can clone it.

Sorry, what?

[IGN-Styly]

in the same program you can clone it.

Sorry, what?

You create a db and then clone it. ie

let db: sled::Db = sled::open("my_db").unwrap();
let db2 = db.clone();

[isbm]

Not sure what it has to do with my original question. The "my_db" is flock'ed at Linux kernel level. If another OS process is trying to open the "my_db", it gets errored.