tracker issue : CF-3043980

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

Bug 87055:(Watson Migration Closure)I propose adding one or more additional attributes to the serializeJSON function that would give the developer more control over how database data is translated into JSON

| View in Tracker

Status/Resolution/Reason: Closed/Won't Fix/

Reporter/Name(from Bugbase): Brian C Swartzfager / Brian C Swartzfager (bcswartz)

Created: 08/19/2011

Components: Language, General

Versions: 9.0.1

Failure Type: Unspecified

Found In Build/Fixed In Build: 0000 /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Mac 10 All

Vote Count: 1

Problem:

I propose adding one or more additional attributes to the serializeJSON function that would give the developer more control over how database data is translated into JSON.  For example, serializeJSON will take the strings "Yes" and "No" and store them in the JSON data as "true" and "false."  Maybe that's per the JSON spec, but if so it would be nice if developers could control those sorts of things.  An attribute-based approach to altering how the data is translated might also provide workarounds to some of the bugs other developers have reported about serializeJSON converting their data in unexpected ways.
Method:


Result:

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

Watson Bug ID:	3043980

External Customer Info:
External Company:  
External Customer Name: Brian C Swartzfager
External Customer Email: 38B04320448B253F99201549
External Test Config: 08/19/2011

Attachments:

Comments:

This bug has been voted..
Vote by External U.
21006 | November 11, 2011 07:31:00 AM GMT
SerializeJSON will now honour the type of the data coming from the DB. So if a string "Yes" is coming from DB, it will be serialized as "Yes" and not as boolean 'true'.
Comment by Rupesh K.
21005 | June 10, 2013 11:09:21 PM GMT