On 8/8/2013 9:02, Rob Vesse wrote:
Sorry I am snowed under with work atm.
Sorry me too - working towards a release.
I have not tested but I would be tempted to enable and change the tests so that they reflect Holger's original regression test case. This would realign the behavior with previous versions of ARQ and fix the regression On a related topic I looked at Holger's question around injecting BNodes into SPARQL updates via ParameterizedSparqlString and it doesn't work in the scenario he describes (an INSERT WHERE) if the variable is used both in the INSERT template and WHERE since the template mention is treated as a minting a fresh BNode. Either he needs to use the BIND workaround discussed by yourself in another thread (http://markmail.org/message/3lsnjq7yca4es2wb) which I suspect is not workable for TQ OR we need to look at restoring initial bindings for updates. I think restoring the feature is going to be the best option, the documentation just needs to be really clear that initial bindings only apply to the WHERE portion of updates and not more generally since that is the only way they were used prior to the feature being removed (I went back and looked at the ARW 2.9.4 code). We can always look at expanding their scope later as we've discussed in the past.
I would appreciate restoring this. I don't understand the last section though - the scenario with pre-bound variables in the INSERT *did* work in 2.9.2. It will be hard to explain to users that INSERT behaves differently from CONSTRUCT. Furthermore, most examples of updates in our code base either take URIs or bnodes as parameters, and if I understand the limitation correctly then I would need to rewrite them all to copy any variable with another BIND.
Thanks, Holger
