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

Well, I guess it's just a personal preference. I don't use aliases, if field names are unique or I use one table. One additional reason for this, that we use special application for Query, so the less characters we put in the field (which would be then evaluated), the better.

Anyway, disregard this part of advice, then.

>>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.