Just to clarify. What SEM_MATCH prefix are you talking about?
A SEM_MATCH based query is indeed a SQL query as SEM_MATCH is a SQL table function. So if you don't want to go through Java APIs or web service endpoint, then running SEM_MATCH directly should give you what you need. Or maybe you just want to see the underlying generated (from SEM_MATCH) SQL query. If that is true, can you please tell us why?
We would like to have the underlying generated SQL query. This is useful for us because we would like to understand how the RDF optimizer works and more useful why it generates certain execution plans. If there is any written document about the optimizer that will be sufficient enough as well. I have searched for such options/document but am not able to find anything yet.
1 person found this helpful
Let's take this offline. Please contact me at matthew dot perry at oracle dot com.