mpagni12 commented on issue #3021: URL: https://github.com/apache/jena/issues/3021#issuecomment-2703204793
Yes it works, it is fast and it return the right number of rows. But it is possibly specific to this query. I have other similar queries where I am quite sure this strategy won't work. Ultimately it may depend on how the intermediary nodes are organised (behind the long property paths), and on the overall database content, which will grow. I found that assigning `?mnet` once in the innermost SELECT and propagating its value to the outermost SELECT, was quite readable (at least to me) and a rather systematic way to formulate such queries. It works as expected in GraphDB. Maybe my question should be converted into a bug report. Anyway, thanks a lot for all the time you spent digging into my problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
