Copy link to clipboard
Copied
Coldfusion 10's behaviour appears to have changed in the evaluation of strings with commas.
Example:
FORM.IDS = 123456, 654321, 789101 (Form Submission)
<cfset fieldname="IDS" />
<cfset test1 = FORM[fieldname] />
<cfset test2 = evalute("FORM.#fieldname#") />
In Coldfusion 9 the value of test1 and test2 is reported as "123456, 654321, 789101".
In Coldfusion 10 the value of test1 and test2 is reported as an array. "Array (3)".
Is this expected behaviour? This is jacking up an application we are trying to upgrade and did not expect this one. Any help will be much appreciated.
Cheers
Lee
Copy link to clipboard
Copied
Was this ever figured out?!
I'm having the same issue and it's holding up the upgrade of a *major* application.
a cfargument of type string used to work fine, but now it's interpreting it as a complex value somewhere....
Copy link to clipboard
Copied
ldavis101 wrote:
Coldfusion 10's behaviour appears to have changed in the evaluation of strings with commas.
Example:
FORM.IDS = 123456, 654321, 789101 (Form Submission)
<cfset fieldname="IDS" />
<cfset test1 = FORM[fieldname] />
<cfset test2 = evaluate("FORM.#fieldname#") /> [BKBK: typo corrected]
In Coldfusion 9 the value of test1 and test2 is reported as "123456, 654321, 789101".
In Coldfusion 10 the value of test1 and test2 is reported as an array. "Array (3)".
Is this expected behaviour?
No, that is unexpected. Please report it as a bug.