"Don't worry about pagination, we can just send the whole database to the front-end" ~ My Boss, being serious AF.

Worst of all, he has worked in system development for 20 years, he is not meant to be this stupid.

I just did that :/

Didn't want to bother with pagination and I'm only expecting about 600 rows max so it shouldn't be a problem for now.

@Florens ya that fines, were expecting that many and more before we even launch. Withing a few weeks it will be closer to tens of thousands.

This is why one of my features is taking so long.
I don't want to send everything at once, so I need to write my own paginator plus API for searching. And I just don't wanna. Especially dont want to touch the JavaScript on the site. I hate mixing JS and rails.

By contrast, the rest of the suite (three quasi-separate applications) use "DataTables" which is a javascript paginator and table sorter that expects all of the data at once. It's present on everything, including a table with tens of thousands of rows. And everyone wonders why it's slow and crashy. 😞

Ugh.

I'm using flask + bootstrap-table. It has support for pagination but it's client side by default and the documentation is kinda bad.

@Root I used datatables a while back, probably round chrome 40, sent 45k rows to the FE and it handled it like a dream, even in ie8

@RTRMS it's actually rather nice until your datasets start getting too large.

I don't like the idea of using a tools I will have to replace. Better to spend extra effort now so you don't have to revisit it later on when you've forgotten how everything works.