tracker issue : CF-3710273

select a category, or use search below
(searches all categories and all time range)
Title:

JSON Parsing Issue due to String Value Treated as a Numeric

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Mary Jo Sminkey / Mary Jo Sminkey (Mary Jo Sminkey)

Created: 02/19/2014

Components: AJAX

Versions: 10.0

Failure Type: Incorrect w/Workaround

Found In Build/Fixed In Build: Final /

Priority/Frequency: Minor / Few users will encounter

Locale/System: English / Platforms All

Vote Count: 0

Problem Description: ColdFusion returned a value from a query as a number that should be been treated as a string. Causing a JSON parsing error. 

Steps to Reproduce: We had a column set as a char that includes string values. When we had a value of '1409315D' in this column being returned in a recordset with trailing spaces due to being a char, CF returned it without quotes, treating it as a numeric value instead and causing a parse issue. A similar test value of 10009290R did not have the same issue. Also if we add code to trim trailing spaces it did not behave this way. 

Actual Result:  \"DATA\":[[1409315D    ,\"Test Product\"]]"

Expected Result:   \"DATA\":[[\"1409315D    \",\"Test Product\"]]"

Any Workarounds: It seems to behave okay if the spaces are trimmed. However considerable amount of time was spent in debugging this issue so should be corrected.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3710273

Deployment Phase:	Release Candidate

External Customer Info:
External Company:  
External Customer Name: MaryJo
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

I thought we were on the latest update, but appears 12 and 13 hadn't been installed yet. We will install and check this bug again to see if it's still there.
Comment by External U.
13473 | February 20, 2014 12:53:06 PM GMT
Actually I got my servers mixed up...the one that this issue was found on was fully patched, running update 13.
Comment by External U.
13474 | February 21, 2014 08:30:50 PM GMT
This bug has been fixed in ColdFusion Splendor. Public beta build can be used to check this. (Comment added from ex-user id:vnigam)
Comment by Adobe D.
13475 | February 26, 2014 11:50:22 PM GMT
So in other words this was NOT fixed on ColdFusion 10. You all really should not be marking a bug as Fixed when you are NOT fixing it for the reported server. This makes it look like Adobe is addressing bugs on these versions at a much higher rate than you are, which simply is not the case.
Comment by External U.
13476 | July 30, 2015 11:45:17 AM GMT
Seeing this issue in CF 11,0,10,300066. What version was it supposedly fixed in?
Comment by Bryan H.
13477 | June 19, 2017 10:52:33 PM GMT