Timeline for Use Of Exists clause in SQL
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2014 at 17:24 | comment | added | Rob Aston | I guess so. Maybe its personal coding styles. I prefer the join way because for me the intention comes across a lot clearer. Especially when it is a big query. | |
| Feb 21, 2014 at 16:55 | comment | added | JeffO | I don't think this makes the intent clearer, but does shed some light for the OP. Exists is pretty explicit in what you're trying to do. To me, a join returns related data from both tables. Using an outer join only to find out what doesn't exist in the other table (and looking for a null) is even more confusing although it is a common technique. When I see exists, I know there are only so many things you could be trying to do. | |
| Feb 21, 2014 at 11:27 | history | answered | Rob Aston | CC BY-SA 3.0 |