Challenge 1 / 1

Why should we avoid using orWhere() and instead use andWhere() with an OR statement inside the query?

andWhere() is faster because it uses better server resources than orWhere().

orWhere() is just outdated and not supported in modern Symfony projects.

Using andWhere() with an OR statement inside gives you more control over the logic, like placing logical parentheses where you want them.

You can't use both conditions in the same statement