The data is coming out as a struct with an array of structs as laid out
by dataTables.
If it was breacking on a special character it would al. The problem
here is, sometimes it works sometimes it doesn't. Putting in the
CFSettings increased it's chance of working.
On 9/9/2015 6:42 PM, 'Alan Holden' via Open BlueDragon wrote:
I think the NS_ prefix is a homage to Netscape, the original Mozilla
browser which spawned Firefox.
How's that for useless trivia?
Seriously though, there seems to be something in the JSON feed which
is breaking the browser at a pretty low level, like AW said.
Have you enclosed all string values within the JSStringFormat tag (to
eliminate the possibility that special characters and quotes are
corrupting the JSON formatting)?
To eliminate the data itself as the cause of the issue, can you try a
similar call against an entirely different table?
Al
On 9/9/2015 11:16 AM, Ernest McCloskey wrote:
I use Firefox and Firebug almost exclusively in my work. That is how
I found out it was a JSON error, or atleast think it is. I just
opened ran the page and after 26.85s, I got:
NS_ERROR_FAILURE:
...SON=Boolean.prototype.toJSON=function(key){return
this.valueOf();};}var cx=/[\u0...
I still haven't gotten to dump to a file, but I do not see how that
matters as I am pulling the exact same data every time, and sometimes
it works, sometimes it does not.
On 9/8/2015 2:28 PM, 'Alan Holden' via Open BlueDragon wrote:
Do you have FireFox with the FireBug plugin?
Other browsers have similar tools, but I find that activating the
Network tab and looking at those result panels while running the app
is a great way to see what's actually coming out of the server.
For example, you might have a data condition (in which one or more
record values is corrupting your JSON flow - begging to be enclosed
in the JSStringFormat tag). That's a guess based on the
unpredictable results you're getting.
HTH,
Al Holden
On 9/8/2015 10:17 AM, Ernest McCloskey wrote:
Ok,
I added the CFSETTING requesttimeout and it seemed to have worked.
Then today, it started not sending the data again. But when I
refresh, it worked. So I am not entirely sure what is going on.
I know that there is no errors in the data because I copied the
code and dumped it to the screen. I will try to write it out to a
file just to see the size of the file. But this did not start
happening until after we got above 2250 records that is was
assembling.
The cfajax call take 50.2 seconds to complete, which does not seem
to be a reason to trigger a time out.
On 9/7/2015 8:39 AM, Alan Williamson wrote:
there is no limit.
i am curious as to what is going on here. How big is your data
on the server side? write it out to a file and see how big that
is and maybe use that to see if there is a problem you are hitting
with the JSON decoded in the browser.
need more details here to start to help. but very curious
On 06/09/2015 17:15, Ernest McCloskey wrote:
I have been messing around with dataTables and passing a initial
table data with a cjajax call. I apparently have hit a cap on
the amount of data cfajax will send back (I believe via JSON).
The current record count is 2290, and it will not send the data
(or there is a time out, not sure).
I have gone in and limited max rows to 2250 and I get the data,
then I tried max rows of 2275 and I do not get anything. I test
the code block and it indeed does create the entire data block as
I can see it all in a CFDUMP.
So does anyone know if there is a setting I can adjust for JSON
response?
Does anyone think it is a timeout issue?
--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
---
You received this message because you are subscribed to the Google Groups "Open BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
