Yeah, I have to look at the two formats again (I think the attribute is queryFormat), but I personally like the default format over the standard format. It has a much smaller footprint, with a lot smaller bit set going over the wire. If I remember correctly though, even the alternate format doesn't conform to what most consider the 'standard' format. I'll have to play around with it tonight...
Steve "Cutter" Blades Adobe Certified Professional Advanced Macromedia ColdFusion MX 7 Developer Co-Author of "Learning Ext JS" http://www.packtpub.com/learning-ext-js/book _____________________________ http://blog.cutterscrossing.com Raymond Camden wrote: > Cool - sorry Cutter. ;) > > FYI, the ability to generate 2 styles of json from a query is also > available in serializeJSON, and can also be used within deserialize as > well. > > On Mon, Jan 12, 2009 at 2:07 PM, Cutter (CFRelated) > <[email protected]> wrote: >> Ray, (Please, call me Cutter.) I want to say I looked at that once >> before, but I just don't remember. At the time, I was also looking to >> write an implementation that would take the JSON return at it's base >> level, without additional attributes. I'll take another look at it >> though, it may be that the non-default may work better... >> >> Steve "Cutter" Blades >> Adobe Certified Professional >> Advanced Macromedia ColdFusion MX 7 Developer >> >> Co-Author of "Learning Ext JS" >> http://www.packtpub.com/learning-ext-js/book >> _____________________________ >> http://blog.cutterscrossing.com >> >> Raymond Camden wrote: >>> Steve, I've admittedly only skimmed your blog post, but could your >>> problem with CF's JSON encode of Queries be fixed with the queryFormat >>> attribute? It's another 'special' attribute like returnFormat. >>> >>> >>> On Mon, Jan 12, 2009 at 11:30 AM, Cutter (CFRelated) >>> <[email protected]> wrote: >>>> That depends on the function's attributes. The returnFormat argument >>>> will automatically serialize the ColdFusion datatype into a JSON object. >>>> I suggest that anyone using it should play with the returns a bit to see >>>> what comes back for the different CF datatypes. Most things are fairly >>>> standard, with the exception of Adobe's implementation of returning a >>>> query. Adobe's implementation provides for a much smaller data return, >>>> but it isn't in the standard format used by most other app servers, so >>>> it requires a small bit of client-side parsing to get the intended >>>> result. Nothing painful, just important to know the difference. I've >>>> written a CFQueryReader object for Ext, to parse CF query returns for >>>> use with Ext components: >>>> >>>> http://blog.cutterscrossing.com/index.cfm/2008/11/20/ColdFusion-Query-Json-Data-Reader >>>> >>> >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:317814 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
