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

---

Query classification of prima:

(num_source_version - num_table - join_type)
S: single
M: multiple
0: not applicable
T: temporal join only
N: non-temporal join only
B: both types of joins
C1: S-S-0
C2: S-M-T
C3: S-M-N
C4: S-M-B
C5: M-S-0
C6: M-M-T
C7: M-M-N
C8: M-M-B