It's bad SQL to get rid of aliases. It takes up no overhead and is esier to read.

>It's obviously better to prepare all constants before SQL than caluclating them in SQL for each record. So, the third example is the best here. Also I would get rid of aliases, since you're using only one table in your SQL.