Weird behavior of bif:st_intersects function

[gone-phishing]

I've posted the SPARQL queries and their outputs here : https://stackoverflow.com/questions/34774647/weird-behaviour-of-bifst-intersects-in-virtuoso-sparql

[openlink]

Can you use the isql tool from virtuoso, make a connection to your virtuoso instance and then paste the query that fails in there and close off with a semicolon.

isql localhost:1111
...
... 
SQL> set sparql_translate on;
SQL> select .......
SQL> set sparql_translate off

You can also try running the query directly via this tool by adding SPARQL in front of your query:

SQL> sparql select ..... 

I would like to see output of both sessions to review.

[openlink]

I made a quick check against the dbpedia.org/sparql endpoint to cross test.

[gone-phishing]

This may sound weird but the problem exists only on the conductor interface. The same query when run using the isql interface works perfectly fine for me.

1. Execute query on the conductor interface -> Fail
2. Execute same query on the isql interface -> Success
3. Go back and execute the same query on conductor interface -> Success

This is weird and I'm not sure if you can reproduce it on your end. So maybe we can close the issue for now unless anyone else faces the same problem :)

[openlink]

Did you use the "Linked Data | SPARQL" page to perform this query via the conductor?

Also what user did you use to authenticate against?

[gone-phishing]

I tried it both on the "Linked Data | SPARQL" conductor interface(using user 'dba') and on the localhost:8890/sparql web interface. In the first step, it failed at both the places.

[pbellini]

I'm having the same problem, I partially solved it using st:distance, also for me with isql (logged as dba) now it works. Restarting the server the problem is there again and also using sparql-auth (user dba) the same query works.