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
predicted = "SELECT professionals.first_name , professionals.last_name FROM professionals JOIN treatments ON professionals.professional_id = treatments.professional_id WHERE treatments.cost_of_treatment<(SELECT AVG( treatments.cost_of_treatment ) FROM treatments)"
gold = "SELECT DISTINCT T1.first_name , T1.last_name FROM Professionals AS T1 JOIN Treatments AS T2 WHERE cost_of_treatment < ( SELECT avg(cost_of_treatment) FROM Treatments )"
I get exact match = 1 for this (using eval_exact_match). Is this by design? Since the predicted SQL has an additional ON clause after the JOIN.
The text was updated successfully, but these errors were encountered:
Consider the below case:
I get exact match = 1 for this (using
eval_exact_match
). Is this by design? Since the predicted SQL has an additionalON
clause after theJOIN
.The text was updated successfully, but these errors were encountered: