Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tolog query optimizer doesn't consider bound variables with value-like() predicate #302

Closed
GoogleCodeExporter opened this issue Mar 16, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?

1. Load the Italian Opera topic map (opera.xtm) into Omnigator

2. Execute the following tolog query:

select $TOPIC
from
 $query = "med*",
 topic-name($TOPIC, $TN),
 value-like($TN, $query) 
?
3. You will get the message:

Error: Variable $query not bound in predicate value-like

What is the expected output? What do you see instead?

Expected to get a list of topics whose name(s) matched "med*"

Please use labels and text to provide additional information.

Ontopia 5.1.0 was used.

The output of Analyze Query is:

Query:

select $TOPIC
from
 $query = "med*",
 topic-name($TOPIC, $TN),
 value-like($TN, $query) 
?

Parsed query:

select $TOPIC from 
value-like($TN, $query)
, =($query, "med*")
, topic-name($TOPIC, $TN)
?


Original issue reported on code.google.com by dan.sp...@gmail.com on 2 Sep 2010 at 6:16

@GoogleCodeExporter
Copy link
Author

The problem here was that the value-like cost estimator was stupidly 
simplistic. Adding a minimum of intelligence to it, so that it doesn't claim to 
be efficient when the second parameter is unbound solves this problem. Done in 
revision 1355.

Original comment by lar...@gmail.com on 8 Sep 2010 at 12:05

  • Changed state: Verified
  • Added labels: Component-Tolog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant