User tests: Successful: Unsuccessful:
This PR fixes the places where multiple ORs are used instead on an IN.
So instead of doing:WHERE id = 1 OR id = 3 OR id = 5
it should be:WHERE id IN (1, 3, 5)
Using IN vs OR:
Test the affected components if they still work ok (admin and frontend):
If possible, also test if there are any negative differences with SQLServer and PostgreSQL.
Status | Pending | ⇒ | New |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2014-08-22 07:29:46 |
Labels |
Added:
?
|
Status | New | ⇒ | Closed |
Status | Closed | ⇒ | New |
Status | New | ⇒ | Pending |
Been lying around for 4 weeks now. So no interest = close.
Status | Pending | ⇒ | Closed |
Closed_Date | 2014-08-22 07:29:46 | ⇒ | 2014-09-20 13:04:39 |
from a code-review point of view as well as MySQLÂ performance point of view all good, makes sense. Thanks Peter!