Hi Sarasi,
I've performed that query with limit 1000, and it worked on one of our
local endpoints, and it ended within 3 minutes.
So I guess that the maximum time allowed for a query on the official
endpoint is relatively low, but the query itself is executable with limit.
Hope that helps.
--
On 5/24/11 8:30 AM, Mohamed Morsey wrote:
Hi Sarasi,
I've performed that query with limit 1000, and it worked on one of our
local endpoints, and it ended within 3 minutes.
So I guess that the maximum time allowed for a query on the official
endpoint is relatively low, but the query itself is
On 5/24/11 1:08 PM, Curran Kelleher wrote:
Greetings,
The problem remains, the following query doesn't execute on the public
DBPedia endpoint
http://dbpedia.org/snorql/?query=select+distinct+%3Fproperty+where+%7B%0D%0A+%3Fs+%3Fproperty+%3Fo.%0D%0A%7D+limit+1,
even with a limit:
select
Hi Kingsley,
Thanks for your clarification, but I don't understand why 'first encounter
!= distinct'. I was thinking that DISTINCT just causes duplicate solutions
to be excluded from the result set, just like DISTINCT in SQL. The SPARQL
reference states
On 5/24/11 3:33 PM, Curran Kelleher wrote:
Hi Kingsley,
Thanks for your clarification, but I don't understand why 'first
encounter != distinct'. I was thinking that DISTINCT just causes
duplicate solutions to be excluded from the result set, just like
DISTINCT in SQL.
Yes, but you are
