I have verified that for large tables like more than 130k rows having 'select' option enabled will lead to RangeError. Is it a bug ?
Possibly, but you're straining the browser with that much data. For over 50k rows, we'd expect serverSide to be used.
serverSide
Colin
Yes Colin I agree. We should have used server side processing here. I just wanted to post this discussion so as to check if this can be confirmed as a bug since some developers might get stuck at this issue in future.
When resources are running low, software typically breaks. So, it's not something we'd be likely to resolve, even if it was a bug.
It looks like you're new here. If you want to get involved, click one of these buttons!
Replies
Possibly, but you're straining the browser with that much data. For over 50k rows, we'd expect
serverSideto be used.Colin
Yes Colin I agree. We should have used server side processing here. I just wanted to post this discussion so as to check if this can be confirmed as a bug since some developers might get stuck at this issue in future.
When resources are running low, software typically breaks. So, it's not something we'd be likely to resolve, even if it was a bug.
Colin