Currently I have a Perl app that reads a config file and creates an SQL "where" clause. For legacy reasons, the clause comes out like this:
where group=1001 or group=1005 or group=1017 or group=1025 I was doing some reading the other day and noticed this could be done like this: where group in (1001,1005,1017,1025) Obviously it is a shorter statement, but is it any better? Currently my app support MySQL 3.23.x and Oracle 8.1.7 which both support the "in" semantic. I could change my app, but I'd like to know if spending a few hours to reconstruct the SQL statement is worth it. --Chuck
