Recently it has been a major topic of ours to secure all data transactions and validate everything as well as possible. Obviously <cfqueryparam> has been a big part of recent blogs and should be coded whenever needed and without exception.
I was trying to format percentages and could not figure out why the number was rounding up to the nearest integer. I did a <cfquery> and did my percentage calculations within a SELECT statement. I then tried <cfoutput> and <cfdump> still showing only integers. I proceeded to try LSNumberFormat and made sure my variables in T-SQL were set to allow decimals. I still had no luck of removing the rounding problem.
Without looking into what cftry actually does, the first thought that popped into my head was probably good for preventing errors. But error handling is sometimes time consuming and you need to know exactly what error could happen. This type of thought is why I overlooked the greatness of the cftry and cfcatch tags. It is extremely easy to use and only makes your code more bullet proof.
Recent Comments