Cannot open read-only about bow HOT 10 CLOSED

Read-only confirmed as working now. Thank you, good sir!

from bow.

This must be some update call bow makes when it's initializing. I'll be checking this later today, and hopefully commit a fix and let you know.

from bow.

Alright, sounds good; please let me know.

from bow.

Okay, I think I found the issue -- when you're Open-ing a brand new database that hasn't been opened before, bow tries to create and store it's meta structure (containing information about buckets) even if it's opened with ReadOnly.

This same problem happens when you access a bucket that doesn't exist -- bow will try to create it regardless of the ReadOnly restriction.

Thanks for reporting this issue, I will fix it and let you know.

from bow.

Excellent. Read-only is a big deal if you access the database from a different process. Inside the same process, one can delegate all Bow operations to a dedicated goroutine and thus avoid dealing with DB locks.

from bow.

Update: I've set up a read-only test, and I'm fixing stuff until it passes. Will let you know.

from bow.

@cbalano

Commit 6703512 resolves this issue.

You can now Open with SetReadOnly(true) and you should be able to read freely, but not write.

Please let me know how it works out for you 😄

from bow.

When I attempt to open read-only in a directory that does not exist, I get a panic, rather than an error. Is that the intended behavior?

from bow.

@cbalano This behaviour is inherited from BadgerDB. Would you prefer to get an error when opening the database instead? Maybe something like ErrNoDatabase?

from bow.

Well, it's a nicety, not a must.

from bow.