Is the JSON too large to parse?

Question

I've fetch a list of schools with their corresponding columns from my database which has a 1000+ rows then convert it to JSON and pass it to my view and parse it using

$.parseJSON('@Html.Raw(Model.subChoiceJsonString)')

then place it to an array

ko.observableArray($.parseJSON('@Html.Raw(Model.subChoiceJsonString)'));

but my problem is it does not work , but it works when there the number of rows are much smaller.

I'm thinking that it can't be parse due to a limitation of a string in Javascript. Is that correct? How can I make it work?

'it does not work'? What is, and what is not working exactly? Any error message? — Bas Slagter, May 30 '13 at 14:43
What does "does not work" mean? Do you receive an error? Is the page too slow to load? Do you get a long running script message in the browser? — Andrew Whitaker, May 30 '13 at 14:43
it could also be a certain record, possibly containing some offending characters. Your server should send the appropriate character encoding — Shanimal, May 30 '13 at 14:45
@Baszz,Andrew it does not display when i display the values ob the array in the table using foreach — Allen, May 30 '13 at 18:21

score 6 · Answer 1 · answered May 30 '13 at 14:44

parseJSON() takes a string.
You're passing it an incorrectly-escaped string literal, which will break if the JSON has single quotes.

Instead, you should use a regular Javascript literal:

var myObject = @Html.Raw(Model.subChoiceJsonString);

Note that this will break if the JSON has U+2028 LINE SEPARATOR; see here.

score 0 · Accepted Answer · answered May 30 '13 at 14:44

0

Yeah that seems like it would be huge... Instead, I would add pagination or something similar to your control. I don't know why a user would want to see 1000+ items at once anyways. Instead, only display 50-100 at a time and allow the user to paginate through the full list.

answered May 30 '13 at 14:44

DigitalZebra

39,494
39
114
146

JSON.parse should have no trouble parsing that. – SLaks May 30 '13 at 14:44
i've used 80,000 row DB table exports in JSON (15mb total footprint); takes about half a sec to parse, but works just fine and instantly after that. – dandavis May 30 '13 at 15:12

score 0 · Answer 3 · answered May 30 '13 at 14:47

0

There are no size limits in HTTP itself, but maybe your server framework imposes some limit. Or maybe which larger responses your HTTP request times out.

answered May 30 '13 at 14:47

blpsilva

69
1
3

Is the JSON too large to parse?

3 Answers3