Then the question is if I open the db with user that has only read-only access - is Orient going to try to open its files in 'rw' mode? Because this is the error we're getting when opening the db on read-only FS - Orient fails because it opens the files in 'rw' mode. I had a look into Orient code and it's possible to pass 'r' mode via URL param, but that will apply only to some files and still for the rest the open mode is harcoded to be 'rw'.
On Tue, Mar 7, 2017 at 8:25 PM, 'scott molinari' via OrientDB < [email protected]> wrote: > Yes, that was the initial intended solution, however, the database could > be locked down over user roles and permissions too. The question is, would > that also offer a proper solution? > > Scott > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- *Karol Pajak | **Software Engineer II* [email protected] <[email protected]> | www.nuix.com Ph: + 61 2 9280 0699 | Fax: +61 2 9212 6902 Level 27, 1 Market Street, Sydney NSW 2000, Australia Twitter: twitter.com/nuix <http://www.twitter.com/nuix> -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
