In any case I think it is awesome. It's the first feature I've seen like this, so thanks for taking a stab at it. In my project having one that works against AG would be immensely useful at times, and I was only hoping for the best when I asked.
Thanks again! Tim On Mon, Nov 2, 2009 at 11:12 AM, Holger Knublauch <[email protected]>wrote: > > Hi Tim, > > I guess you are talking about > > > http://composing-the-semantic-web.blogspot.com/2009/11/sparql-debugger-and-profiler.html > > The SPARQL debugger works on any database, but it always need to go > through the ARQ interface to talk to that database. By default TBC > will execute SPARQL over the union graphs and thus never see any > native optimizations of the particular DB. The option "query on base > graph only" that would otherwise have it run directly on the DB is not > used by the Debugger, at least not yet. I am not sure how useful that > would be, but I'll put it on my list to investigate. TBC 3.2.0 > includes the first release of the Debugger and I am sure some people > will have feedback - it's a very new and therefore experimental feature! > > So I guess the short answer is "no". > > Holger > > > On Nov 2, 2009, at 10:56 AM, Tim Harsch wrote: > > > Looks like the new SPARQL debugger and profiler work only when > > executing SPARQL natively. Does it work when the datastore is in > > AllegroGraph? Or, could it be made to work that way? > > > > Thanks, > > Tim > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
