On databases lacking XOR, Q(…) ^ Q(…) ^ Q(…) wrongly interpreted as exactly-one rather than parity Description
On databases lacking XOR, Q(…) ^ Q(…) ^ Q(…) wrongly interpreted as exactly-one rather than parity Description: a task in Lego-RL-SWE-Bench-Verified (Harbor dataset). On databases that don’t natively support XOR, such as PostgreSQL, Django generates incorrect fallback SQL for Q(…) ^ Q(…) ^ Q(…)…
The task
On databases that don’t natively support XOR, such as PostgreSQL, Django generates incorrect fallback SQL for Q(…) ^ Q(…) ^ Q(…) with more than 2 arguments. The correct interpretation, and the interpretation of databases natively supporting XOR (e.g. MySQL), is that a ^ b ^ c is true when an odd number of the…
Part of Lego-X/Lego-RL-SWE-Bench-Verified.