Error: Cannot attach an Insert or Delete query to the selected resource in TBC

10 views
Skip to first unread message

Tim Smith

unread,
Jun 9, 2020, 4:23:13 PM6/9/20
to topbrai...@googlegroups.com
Hi,

Working in TBC 6.3.1/Windows 10, I attempted to attach the queries I had developed in the SPARQL window.  The attempt worked fine for Select and Construct queries but would not allow me to attach INSERT or DELETE queries. 

Can TBC be changed to support attaching update queries?

Thanks,

Tim

Here's the error:

org.apache.jena.query.QueryParseException: Encountered " "insert" "INSERT "" at line 1, column 1.
Was expecting one of:
    "\ufeff" ...
    "base" ...
    "prefix" ...
    "select" ...
    "json" ...
    "describe" ...
    "construct" ...
    "ask" ...
   
at org.apache.jena.sparql.lang.ParserARQ.perform(ParserARQ.java:100)
at org.apache.jena.sparql.lang.ParserARQ.parse$(ParserARQ.java:52)
at org.apache.jena.sparql.lang.SPARQLParser.parse(SPARQLParser.java:34)
at org.apache.jena.query.QueryFactory.parse(QueryFactory.java:147)
at org.topbraid.jenax.util.ARQFactory.doCreateQuery(ARQFactory.java:207)
at org.topbraid.jenax.util.ARQFactory.createQuery(ARQFactory.java:237)
at org.topbraidcomposer.sparql.view.actions.SaveQueryAction.run(SaveQueryAction.java:40)
at org.topbraidcomposer.ui.views.AbstractViewAction.run(AbstractViewAction.java:69)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:247)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
at org.eclipse.jface.action.ActionContributionItem.lambda$5(ActionContributionItem.java:436)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4418)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4236)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3824)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)

Holger Knublauch

unread,
Jun 9, 2020, 6:36:39 PM6/9/20
to topbrai...@googlegroups.com

Hi Tim,

this ability to attach queries to resources is very old and hasn't seen much use or attention in recent years. Here, the property spin:query is used, with the range of sp:Query, not sp:Update. Any of these are stored in SPIN RDF syntax, while we have (e.g. in SHACL) moved to storing them as strings.

I'd suggest to use other mechanisms to save the query, e.g. make up your own string property to paste it into from TBC, or save them to a text file, or use TopBraid EDG to manage your queries - it has a SPARQL Library panel for that purpose:

In general, I recommend trying to move tasks from TBC to EDG. If you discover "missing" features that are only in TBC and that block you from using the EDG UI that is bundled with TBC-ME, please let us know.

Holger

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CAF0WbnJ-vbSoKZ67jqf9uEDYYsE_bgcS%2B1R8tLaWyKtcKLxnRw%40mail.gmail.com.

Tim Smith

unread,
Jun 10, 2020, 9:51:32 AM6/10/20
to topbrai...@googlegroups.com
Thanks Holger,

I have soooo many text files full of SPARQL queries :)  which is what I used here.  I'll move to the EDG SPARQL Library going forward.

I am slowly moving to EDG.  It really comes down to not having enough time to learn EDG vs needing to get something done so I go back to what I know when time is short.

Thanks,

Tim






Reply all
Reply to author
Forward
0 new messages