INNER JOIN ON vs WHERE clause

Re:INNER JOIN ON vs WHERE clause by Izkata on Wednesday October 30, 2024 @07:47AM (#41993873)

I tend to find table aliases a step down in readability, and only use them as necessary, because now your eyes have to jump up and down to see where the columns come from.

[ Parent | on HN ]

Re:INNER JOIN ON vs WHERE clause by ausp on Wednesday October 30, 2024 @07:58AM (#41993929)

The aliases don't force you to follow each one through; eyes can do no jumping if you like in either case.

But if you can't infer from the column name which table they will come from, I find having the option to check far more preferable to that of having no way of knowing.

[ Parent | on HN ]

Re:INNER JOIN ON vs WHERE clause by rbanffy on Wednesday October 30, 2024 @08:46AM (#41994228)

I think the aliases in the example are very intuitive - it's easy to correctly guess where they come from.

[ Parent | on HN ]

Re:INNER JOIN ON vs WHERE clause by Suppafly on Wednesday October 30, 2024 @03:27PM (#41999185)

>I tend to find table aliases a step down in readability

I suppose it depends on your database, one of the ones I work with all the time has crazy long table and view names and aliases make resulting SQL more readable.

[ Parent | on HN ]