That was a hurried grab that included an intentional SELECT Query not
made by the PHP, but rather from the Fuseki web app to check that my
post was actually being implemented. (I had just finished chasing a
bug in a DELETE DATA that didn't quite match a previous INSERT DATA).
What I'm posting with curl_post to ds/update is generally one of
three patterns:
INSERT DATA {GRAPH<http://localhost/node1/server/feeds> {
<http://localhost/node1/server/feed/4fce22b5a6acb> dc:date
"2012-06-05T16:39:40-04:00" . } }
DELETE DATA {GRAPH<http://localhost/node1/server/feeds> {
<http://localhost/node1/server/feed/4fce22b5a6acb> dc:date
"2012-06-05T16:39:40-04:00" . } }
LOAD<http://localhost/data/marinespecies.org.taxname.127160.rdf>
There are also some SPARQL SELECTs which I send with curl_get to
ds/query, without problem. For the posts, I could trace all my issues
to badly constructed content on my part.
Correct me if I'm wrong---I don't think you are telling me to
send the INSERT, DELETE, and LOAD to ds/query as a post. I vaguely
recall that when I tried that Fuseki carped about it.
I'll make a clean, minimal set of service calls and send you the result.
On Tue, Jun 5, 2012 at 5:43 PM, Andy Seaborne <[email protected]> wrote:
> On 05/06/12 21:59, Bob Morris wrote:
>>
>> I start with
>> ./fuseki-server --update --mem --debug /ds
>> logging comes to the shell.
>>
>> Here's a bit of recent log.
>>
>> 16:44:58 INFO Fuseki :: [219] OK/select
>> 16:44:58 INFO Fuseki :: [219] 200 OK
>> 16:44:58 INFO Fuseki :: [220] POST
>> http://localhost:3030/ds/update
>
>
> That's not a query :-)
>
> In SPARQL query != update.
>
> To POST a query, POST it to /ds/query
>
>
>> 16:44:58 INFO Fuseki :: [220] 200 OK
>
>
> So it's an HTML form POSted update (you get 204 otherwise).
>
>
>> 16:44:58 INFO Fuseki :: [221] POST
>> http://localhost:3030/ds/update
>> 16:44:58 INFO Fuseki :: [221] 200 OK
>> 16:45:09 INFO Fuseki :: [222] GET
>>
>> http://localhost:3030/ds/query?query=SELECT+*+WHERE+%7B%0D%0A+GRAPH+%3Fg+%7B%3Fs+%3Fp+%3Fo%7D%0D%0A%7D+LIMIT+10&output=xml&stylesheet=%2Fxml-to-html.xsl
>> 16:45:09 INFO Fuseki :: [222] Query = SELECT * WHERE {
>> GRAPH ?g {?s ?p ?o} } LIMIT 10
>> 16:45:09 INFO Fuseki :: [222] OK/select
>> 16:45:09 INFO Fuseki :: [222] 200 OK
>>
>>
>> Leaving for a train now. Tonight or tomorrow will try to produce a
>> complete minimal log and also report what (I believe that) the POST
>> arguments are.
>
>
> Please do - looks like you are POSTing an update HTML-form style.
>
> Updates don't log. Form submitted updates are buffered - the entire string
> is available to be printed but ones sent as "application/sparql-update" are
> stream read (e.g. a large INSERT DATA { .... })
>
> I've fixed the server so if started with "--debug" you will get update
> logging (and a lot of other logging - debug mode). Old feature - got lost
> when config files were added.
>
> It'll be in tonight's build.
>
> Andy
>>
>>
>> Thanks
>> Bob
--
Robert A. Morris
Emeritus Professor of Computer Science
UMASS-Boston
100 Morrissey Blvd
Boston, MA 02125-3390
IT Staff
Filtered Push Project
Harvard University Herbaria
Harvard University
email: [email protected]
web: http://efg.cs.umb.edu/
web: http://etaxonomy.org/mw/FilteredPush
http://www.cs.umb.edu/~ram
===
The content of this communication is made entirely on my
own behalf and in no way should be deemed to express
official positions of The University of Massachusetts at Boston or
Harvard University.
