Home/ Questions/Q 7046719
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T02:41:03+00:00

I’m currently developing a Zend Framework project, using Doctrine as ORM. I ran into

  • 0

I’m currently developing a Zend Framework project, using Doctrine as ORM.

I ran into the typical situation where you have to show a list of items (around 400) in a table, and of course, I don’t want to show them all at once.
I’ve already used Zend_Paginator before (only some basic usage), but i always used to get all the items from the DB, and then paginate them, but now it doesn’t feel quite right.

My question is this: is it better to get all items from DB first and then “paginate” them, or to get “pages” of items as they are requested? which would have a larger impact on performance?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    For me, it is better to get a part of the data and then paginate through them.

    1. If you get All the data from a DB you paginate with the help of JavaScript.
      The first opening of the page will take a long time (for 400 rec. is OK).
      Browser has a limited memory. If a user opens up a lot of tabs in the browser
      and you take a lot of memory (with your data)
      this will slow down the speed of the browser and the speed of your application.
      You have only 400 records but the increase of the data happens very often.
      At worst, the whole browser may break when the page is opened.
      What if browser doesn’t support JS …

    2. If you get part of the data from DB, the only defect is if
      a user has a very slow Internet speed(but this is the defect in the first option – in the first refresh of the page).
      If someone wants to get to another page, it will take a little bit longer than JavaScript.

    The second option is better(for me) in the long run, because if it works it will work for years.

    • 0