Re: [Virtuoso-users] read only db?

2017-09-22 Thread Hugh Williams
 Jörn,

> On 21 Sep 2017, at 21:00, Jörn Hees  wrote:
> 
> 
>> On 21 Sep 2017, at 19:23, Hugh Williams  wrote:
>> 
>> read-only in what sense, as if you query the Virtuoso default /sparql 
>> endpoint it is in read only mode, thus if that is all that is exposed it 
>> cannot be modified ?
> 
> No, even stricter... read only down to filesystem level as in "no bit 
> changes" in the virtuoso.db file (and also no meta-data of that file).
> 
> If not possible with the main DB file, is it maybe possible with 
> "secondaries" or anything like that? (to minimize the size of the DB file 
> that is modified on each run)?

[Hugh] This is not possible as there are internal process within Virtuoso 
itself that need write access to the database.

Regards
Hugh

> 
> Best,
> Jörn
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users



smime.p7s
Description: S/MIME cryptographic signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users


Re: [Virtuoso-users] read only db?

2017-09-21 Thread Jörn Hees

> On 21 Sep 2017, at 19:23, Hugh Williams  wrote:
> 
> read-only in what sense, as if you query the Virtuoso default /sparql 
> endpoint it is in read only mode, thus if that is all that is exposed it 
> cannot be modified ?

No, even stricter... read only down to filesystem level as in "no bit changes" 
in the virtuoso.db file (and also no meta-data of that file).

If not possible with the main DB file, is it maybe possible with "secondaries" 
or anything like that? (to minimize the size of the DB file that is modified on 
each run)?

Best,
Jörn


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users


Re: [Virtuoso-users] read only db?

2017-09-21 Thread Hugh Williams
Hi Jörn,

read-only in what sense, as if you query the Virtuoso default /sparql endpoint 
it is in read only mode, thus if that is all that is exposed it cannot be 
modified ?

Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc.  //  http://www.openlinksw.com/
Weblog   -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter  -- http://twitter.com/OpenLink
Google+  -- http://plus.google.com/100570109519069333827/
Facebook -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers



> On 20 Sep 2017, at 10:58, Jörn Hees  wrote:
> 
> Hey,
> 
> is there a way to run virtuoso in read-only mode, i.e., so the virtuoso.db 
> file doesn't get modified but i can SPARQL against it?
> 
> I'm asking cause this would incredibly ease scientific use cases with docker 
> etc. and allow us to package whole ready-to-run containers e.g. for various 
> DBpedia releases.
> 
> Cheers,
> Jörn
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users



smime.p7s
Description: S/MIME cryptographic signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users


[Virtuoso-users] read only db?

2017-09-20 Thread Jörn Hees
Hey,

is there a way to run virtuoso in read-only mode, i.e., so the virtuoso.db file 
doesn't get modified but i can SPARQL against it?

I'm asking cause this would incredibly ease scientific use cases with docker 
etc. and allow us to package whole ready-to-run containers e.g. for various 
DBpedia releases.

Cheers,
Jörn


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users