How to make pagination?
Mishra Anshu
Ranch Hand
Posts: 224
posted 12 years ago
Hi,
This is a very common problem for any web application.
I need to make search which may result in thousands of records.
So, accordingly the page will be displayed (say, 10 results per page).
1st Approach:-
I make the query to hit database everytime a search is requested.So, for every page a search is unnecessarily performed.
2nd Approach:--
I store the result in the meory. So, say 1000 record have been searched and stored in the memory. So, not for every page result a new search is
required. But..., here I can't predict the search size, so I may get OutOFMemoryException.
3rd Approach :-
Since my DB is Oracle. I want to make a temp table to store the result od the search. But in Oracle , I think there is only Global Temp table, So, How it can handle the search , if there are multiple persons making the search at the same time.
:roll:
This is a very common problem for any web application.
I need to make search which may result in thousands of records.
So, accordingly the page will be displayed (say, 10 results per page).
1st Approach:-
I make the query to hit database everytime a search is requested.So, for every page a search is unnecessarily performed.
2nd Approach:--
I store the result in the meory. So, say 1000 record have been searched and stored in the memory. So, not for every page result a new search is
required. But..., here I can't predict the search size, so I may get OutOFMemoryException.
3rd Approach :-
Since my DB is Oracle. I want to make a temp table to store the result od the search. But in Oracle , I think there is only Global Temp table, So, How it can handle the search , if there are multiple persons making the search at the same time.
:roll:
"Ignorance is bliss"
Mishra Anshu
Ranch Hand
Posts: 224
posted 12 years ago
Mishra,
For Oracle, look into materialized views. It's a caching technology on the db server.
If you are writing your own (options 1/2), consider whether you need all the results. A lot of users abandon the search without paging at all. In that case you only need the first 20 or so records. Getting more is a waste of resources.
For Oracle, look into materialized views. It's a caching technology on the db server.
If you are writing your own (options 1/2), consider whether you need all the results. A lot of users abandon the search without paging at all. In that case you only need the first 20 or so records. Getting more is a waste of resources.
[OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
| It is sorta covered in the JavaRanch Style Guide. |