Ok, great that the problem has been solved.

We can wait to the next release to fix this, so is not necessary to create
the snapshot archive.

Thanks.
Z.

On Mon, Feb 22, 2010 at 2:46 PM, Hugh Williams <hwilli...@openlinksw.com>wrote:

> Hi Ricardo,
>
> I was able to recreate your problem with the 6.1.0.3126 build, but testing
> against  the latest 6.1.0.3127 build we have internally this issues has been
> resolved:
>
> $ /opt/virtuoso/bin/isql 1111
> Connected to OpenLink Virtuoso
> Driver: 06.01.3127 OpenLink Virtuoso ODBC Driver
> OpenLink Interactive SQL (Virtuoso), version 0.9849b.
> Type HELP; for help and EXIT; to exit.
> SQL> sparql select * from <http://localhost:9999> {?s ?p ?o};
> s
>       p
>             o
> VARCHAR
>       VARCHAR
>             VARCHAR
>
> _______________________________________________________________________________
>
>
> 0 Rows. -- 71 msec.
> SQL> sparql insert into graph <http://localhost:9999> {<
> http://localhost:9999/x> <http://www.w3.org/2000/01/rdf-schema#label>
> "test"};
> callret-0
> VARCHAR
>
> _______________________________________________________________________________
>
> Insert into <http://localhost:9999>, 1 triples -- done
>
> 1 Rows. -- 221 msec.
> SQL> sparql select * from <http://localhost:9999> {?s ?p ?o};
> s
>       p
>             o
> VARCHAR
>       VARCHAR
>             VARCHAR
>
> _______________________________________________________________________________
>
> http://localhost:9999/x
>         http://www.w3.org/2000/01/rdf-schema#label
>                test
>
> 1 Rows. -- 1 msec.
> SQL> sparql delete from <http://localhost:9999> { <http://localhost:9999/x>
> <http://www.w3.org/2000/01/rdf-schema#label> "test" } where { graph <
> http://localhost:9999> { <http://localhost:9999/x> <
> http://www.w3.org/2000/01/rdf-schema#label> "test" } };
> callret-0
> VARCHAR
>
> _______________________________________________________________________________
>
> Delete from <http://localhost:9999>, 1 triples -- done
>
> 1 Rows. -- 32 msec.
> SQL> sparql select * from <http://localhost:9999> {?s ?p ?o};
> s
>       p
>             o
> VARCHAR
>       VARCHAR
>             VARCHAR
>
> _______________________________________________________________________________
>
>
> 0 Rows. -- 1 msec.
> SQL>
>
> So a fix will be available in the next release due out soon, or I can
> possibly arrange a snapshot archive for you to get this fix ...
>
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software
> Web: http://www.openlinksw.com
> Support: http://support.openlinksw.com
> Forums: http://boards.openlinksw.com/support
> Twitter: http://twitter.com/OpenLink
>
> On 22 Feb 2010, at 16:38, Ricardo Z wrote:
>
> Hi.
>
> We are having some problems related to triples deletion when the object is
> a literal string with no language.
> (We are using virtuoso 6.1.0.3126)
>
> As an example consider the following.
> We clear the graph, them we insert a triple, we query the graph and we
> obtain the triple. Following we delete the triple we received feedback about
> the triple
> deletion, but if we query it again, the triple is still retrieved.
>
> See.
> sparql clear graph <http://localhost:9999>;
> sparql insert into graph <http://localhost:9999> {<http://localhost:9999/x>
> <http://www.w3.org/2000/01/rdf-schema#label> "test"};
> sparql select * from <http://localhost:9999> {?s ?p ?o};
> sparql delete from <http://localhost:9999> { <http://localhost:9999/x> <
> http://www.w3.org/2000/01/rdf-schema#label> "test" } where { graph <
> http://localhost:9999> { <http://localhost:9999/x> <
> http://www.w3.org/2000/01/rdf-schema#label> "test" } };
> sparql select * from <http://localhost:9999> {?s ?p ?o};
>
> The output is:
>
> Clear <http://localhost:9999> -- done
> No. of rows in result: 1
> --------
> Insert into <http://localhost:9999>, 1 triples -- done
> No. of rows in result: 1
> --------
> http://localhost:9999/x     http://www.w3.org/2000/01/rdf-schema#label
> test
> No. of rows in result: 1
> --------
> Delete from <http://localhost:9999>, 1 triples -- done
> No. of rows in result: 1
> --------
> http://localhost:9999/x     http://www.w3.org/2000/01/rdf-schema#label
> test
> No. of rows in result: 1
>
> But if instead we insert a triple with the string literal object setting
> the language, everything works fine.
> See.
> sparql clear graph <http://localhost:9999>;
> sparql insert into graph <http://localhost:9999> {<http://localhost:9999/x>
> <http://www.w3.org/2000/01/rdf-schema#label> "test"@en};
> sparql select * from <http://localhost:9999> {?s ?p ?o};
> sparql delete from <http://localhost:9999> { <http://localhost:9999/x> <
> http://www.w3.org/2000/01/rdf-schema#label> "test"@en } where { graph <
> http://localhost:9999> { <http://localhost:9999/x> <
> http://www.w3.org/2000/01/rdf-schema#label> "test"@en } };
> sparql select * from <http://localhost:9999> {?s ?p ?o};
>
>
> Output is:
> Clear <http://localhost:9999> -- done
> No. of rows in result: 1
> -------
> Insert into <http://localhost:9999>, 1 triples -- done
> No. of rows in result: 1
> -------
> http://localhost:9999/x     http://www.w3.org/2000/01/rdf-schema#label
>  test
> No. of rows in result: 1
> -------
> Delete from <http://localhost:9999>, 1 triples -- done
> No. of rows in result: 1
> -------
> No. of rows in result: 0
>
>
> Also works if instead of using a literal, we use a url.
>
> We observed the same problem when we modify the graph, which instead of
> modify the graph, only add the new triple value. We suppose this problem is
> related to triples deletion problem.
>
> Thanks.
> Z.
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
>
> http://p.sf.net/sfu/intel-sw-dev_______________________________________________
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>
>
>

Reply via email to