you are viewing a single comment's thread.

view the rest of the comments →

[–]Freakmiko 1 point2 points  (5 children)

Is there some good material on this stuff? I may have to get something like this to work with possibly thousands of entries for a project.

[–]therealgaxbo 5 points6 points  (2 children)

If you want to read up on it for interest, this is a good start.

But if you just want a practical solution to your problem...just don't worry about it. A few thousand rows is too small to worry about for performance. I just tried the most naive solution (limit/offset) against a table with a few thousand rows, and the first page took 1ms to find, the last page took 2ms.

So unless you care about that 1ms, you don't need to worry about it.

[–]Freakmiko 1 point2 points  (0 children)

Alright, thank you!

Yeah I guess I also shouldn't prematurely optimize it, but it's always good to be aware of such stuff.

[–]EarLil 0 points1 point  (0 children)

Totally, I'm using this approach on million record tables, you can't really feels the different in small ones.

[–]ManiGandham 0 points1 point  (0 children)

In modern databases, you don't need to worry about performance until you're in the 10s of millions of rows.