To be honest, I would like the documentation to go in the other direction, and give less information. There are two cases where I need column names to be predictable:
1) I used <code>AS</code> in my SQL code.
2) I used SELECT *, possibly with a <code>JOIN<Join> such as
<pre>SELECT albums.*,artists.*
FROM albums INNER JOIN artists ON album.artist = artist.id</pre>
I don't want programs depending on column names for anything else. Not only because the values returned differ in different SQL implementations, but because it shows shoddy programming. Yes, it's a little more work having to scatter <code>AS</code> around your code, but at least you know what's going to happen.