It turns out my a rewrite wasn't to terrible. I added 1 line of code. :) And apparently I had forgotten I wrote my query restructuring code to account for a change on another site. I remember now that ColdFusion gave me 1 format and OpenBD gave me the other format. Then on top of that I forgot to copy that rewrite into my default site setup.
But it is nice to know I can control how openbd hands me data. ----- Original Message ----- From: "Alan Williamson" <[email protected]> To: [email protected] Sent: Sunday, July 1, 2012 5:47:31 PM Subject: Re: [OpenBD] Change on CFAJAXPROCY JSON output We changed that to come inline with the output other engines are kicking out. See my [ANN] email earlier this week ... you have full control over this, including setting what the default is in bluedragon.xml so you don't have to go back and rework your code. Historically we lower-cased everything; now the default is to maintain. This is why we have the nightly build ... to shake out some of these things. We wanted to hold back this release until others had their big releases so we could tighten things up accordingly. On 01/07/2012 17:32, [email protected] wrote: I admit I have been slacking on the message boards, but can someone tell me when in the past couple months the cfajaxproxy response from the server went from all lower case (columns, data) to all caps? I just did a nightly update a server to the new nightly build to get the broken cfc working (was using the official download from several months past). That's not the only bits, it appears that all the data coming from the query now retains capital letters in fields that had capital letters. I am hoping this is more of an oops bug verses new function as I now need to go back through and rewrite a few sites to handle the new json format coming back from the site. -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en
