Re: [SMW-devel] execute #ask query internally

[<ki...@gm...>]

On 06/05/2014 20:37, Jeroen De Dauw wrote:
> Hey,
> Note that Markus his email is 6 years old, some things have changed since then :)

I'm sure they have! nevertheless, it was one of the few references to internal ask queries that I found.

> If what you want to visualize is not the query result of an ask query, then using the result printer infrastructure is not the way to go. I suggest you instead create a parser function that has an interface suited for the task at hand. Once it is clear what the inputs of this function are and what you want to get out of it, we can determine what the most efficient way to talk to the SMW store is.

That's interesting, maybe the way to go is a parser function, although right now, please forgive me for concentrating fully on my current implementation issue, I have a deadline.  :-)
As I've started with the SRF printer, I'll finish, maybe later go back and see if something else is more appropriate, taking into account what you say about wikibase.
Many times I have wished I was just dealing directly with a database and could just get the data I want and focus on the d3 implementation..

Having said that, the input to the printer is essentually the result of an #ask query, it's all about displaying relationships using D3 graphics.
However, I struggled to find how to get ask to give me results like SQL JOINS, and using a template containing further ask queries was messy and doesn't really work, so or the moment, I decided to loop within the printer code to "drill down" and create the relationship tree.

I'm still totally stumped on how to deal with the picture file stuff in the ask queries, I can see the foto 'column' result in the ask query if I var_dump() the result object, but there is no sign of the image file name in there. any ideas?

Thanks!

k/