You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Parisa Ataei edited this page Mar 26, 2019
·
12 revisions
Initial idea
num_variations_query_ran_on_it - num_choices_in_the_query -
max_num_table - max_num_joins
S: single
M: multiple
0: not applicable
Notes:
A good start would be to classify queries based on the
number of choices and joins.
We may want to classify based on nested choices?! do we
have types of choices or anything like the type of joins? Ask Eric
Also consider max num table bc we may have different num table
in different variants of the vquery.
I don't think the num of variations the query run on is really a
feature of the query. It's rather related to the database. So
should we still consider it? Discuss with Eric