Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Display records (more than 200K rows)

Status
Not open for further replies.

aas1611

Programmer
Dec 14, 2001
184
DE
Hallo,

I'written a PHP Code that retrieves records of around 200K from MySQL table. But it seems the records shown on Internet Explorer are not more than 10K (or at least I know it doesn't show all records).

Is there a way to show records more than 200K on Internet Explorer using PHP? Maybe in multiple pages or something?

Thanks for any clues!
 
With so many rows you're bound to have issues with timing out and overall the page won't be very useful. So pagination (breaking up into multiple pages) is the best option. I suggest you look at this helpful FAQ about data paging. It should get you started.
 
Do you expect your users to read all of the records at once??

You are probably running over the default run time of 30 seconds. See <
I believe there is an entry in thd FAQ section on how to page.

Ken
 
Thanks for your ideas. I will look into the FAQs further.

I don't expect my users to look at all these records at once, but I want that my application is able to retrieve all of the records. I should have more limitations on how the data should be retrieved.

:))
 
Just got to my head, is there a certain limit of number of records shown on IE?

Thanks!
 
You should always be very careful of presenting lots of data on a single web page.
I did this once on a page that was just meant as a dumb report and was not even served by a webserver. It was simply meant to be opened and read as a dumb html file and it crashed the machine. I hadn't bothered to check how much data the script would produce and the machine died as a consequence. The guy that opened my report was doing other important work at the time and you can guess how happy he was to lose all his work for that morning!
The moral of the story is to never try to generate much data for a browser to cope with. Even small documents can often require large chunks of memory to manage since images, layout, formatting and other non-obvious data has to be maintained for the browser to be able to scroll around effectively. I found IE to be the worst for this but that is probably not relevant. The issue is, keep your pages short.
If you have to have large documents, consider using something different to manage the data like acrobat and pdf.

If you want to remain popular with your viewing public then don't risk crashing their machines!

Good luck!

:)




(slowly healing) Trojan.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top