> Heres a real world scenario I've come across: > > Code throughout the app is using data returned from a query that has > select *, and pulls data from more than one table. > Someone adds a column to one of the tables in the query that has the > same name as a column in another of the tables in the query. > > CF now returns a query with 2 columns named the same and your data is > funked up all over the site because using query.columnname is > referencing the wrong column.
Some people disagree with this, but I recommend using a naming convention that makes this impossible. In other words, one where the table name can be inferred from the column name. Nick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:246130 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
