Spike wrote:
Ah I had a feeling that was going to come up. If you are displaying a query and not allowing for it to be empty. That IMO is a poor choice and is in fact playing into the part of a lazy coder.
I'm not sure I follow what you're saying there.
Are you saying it's bad to create a query without the full list of columns or something else?
I meant that if you are not expecting an empty query object you should explicitly set the columns within the queryNew(). It would be bad not to.
I know your talking about the same thing and you feel that is more overhead than you would like.
Hence the nice addition of the var scoped variables at the top of the function.
Not sure I understand what you're getting at here either.
We may not be thinking the same thing. If you needed to change from an array to a structure you would just change the var from <cfset var myVar=arrayNew(1) to <cfset var myVar=structNew()>
That means that I will take great care to do things now that will avoid more work down the line. That's what an awful lot of people seem to do. I was being flippant when I described it as laziness. I should probably have described in terms of minimizing the total cost of a project or some such.
I though you meant Lazy as in I'm not going to plan for the future. We both agree on avoiding work down the line. However in many cases when you can just glance at the var variables and know their types without having to track it down that indeed saves work down the road.
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
