Re: [Virtuoso-users] Bug with upgrade Virtuoso 6.1.6 to 7.0.0

2013-10-23 Thread Hugh Williams
Hi Julien, Can you please confirm if you are using the stable or develop 7 branch in git ? Also, what does the following query directly against the RDF_QUAD table report as the number of graphs: select distinct count(distinct g) from rdf_quad; Best Regards Hugh Williams Professional Se

[Virtuoso-users] Bug with upgrade Virtuoso 6.1.6 to 7.0.0

2013-10-23 Thread Julien Plu
Hi, I try to upgrade my old Virtuoso version (6.1.6) to the new one (7.0.0) but in keeping the same virtuoso.db file. So I saved the "virtuoso.db" file, deleted completely the 6.1.6 virtuoso version, installed the 7.0.0 version, put the "virtuoso.db" file in the "db" folder then start the new Vir

Re: [Virtuoso-users] Insert trigger on RDF_QUAD fires twice

2013-10-23 Thread Markus Freudenberg
Hello, any trigger syntax will do, e.g.: create trigger BLUB AFTER INSERT on DB.DBA.RDF_QUAD REFERENCING NEW AS N { if(N.G IS NOT NULL AND N.S IS NOT NULL AND N.P IS NOT NULL AND N.O IS NOT NULL) { INSERT INTO A_TRIPLETEST VALUES(N.G, N.S, N.P, N.O, now()); } } after executing this: SPARQL PREF

Re: [Virtuoso-users] Insert trigger on RDF_QUAD fires twice

2013-10-23 Thread Jürgen Jakobitsch SWC
hi sebastian, is the source code of your trigger available to take a look at it? in any case, a "set triggers off;" might be useful [1]. wkr jürgen [1] http://docs.openlinksw.com/virtuoso/TRIGGERS.html On Wed, 2013-10-23 at 11:55 +0200, Sebastian Tramp wrote: > On Wed, Oct 23, 2013 at 11:49:23

[Virtuoso-users] Insert trigger on RDF_QUAD fires twice

2013-10-23 Thread Sebastian Tramp
On Wed, Oct 23, 2013 at 11:49:23AM +0200, Markus Freudenberg wrote: Dear list and Hugh esp., one of our students here has an issue with insert triggers, can you please look into it: > I noticed, that every triple inserted in the virtuoso quad-table will cause > an insert trigger to fire twice (v

Re: [Virtuoso-users] Lost connection to server

2013-10-23 Thread Julien Plu
Hi Hugh, I didn't retried to run my script after, but I think you had right in saying that it can come from a reboot of Virtuoso. Because in looking the Virtuoso log file I see a reboot at a time around the connection error. I gonna retest my script when I will access to this machine which is now