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
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
Back on 2.5.2 or so I encountered the same thing. I didn't need it bad
enough so didn't investigate further.
On Tue, Sep 1, 2009 at 8:25 AM, flatters helenlflat...@googlemail.comwrote:
Yeah... that's what we though but it doesn't seems to be working for
us - just returns a message saying it
How can I import N3 data into TBC? I want to view N3 data, but TBC
complains if I try to open the file directly. I know there is a way to
export to this format? How about import?
Tim
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
for work on
AllegroGraph.
Holger
On Jan 29, 2009, at 7:58 AM, Tim Harsch wrote:
I forgot to mention: I'm on TBC 3.0 beta1
Thanks!
On Wed, Jan 28, 2009 at 1:40 PM, Tim Harsch harschw...@gmail.com wrote:
I think we are on the right track Scott. That is what I thought at first
too. In fact
Hi all,
I am trying to open a pre-existing AG data store. I go to
File-New-RDF/OWL Alelgrograph database. Provide the path of the store and
the database name, make sure to leave Overwrite existing database
unchecked. It then creates the .allegro file and what not, but stomps the
original store.
