The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
I have done some testing on searching through largish flat file databases, and although it was rather crude and contained repeating data, searching through a 10,000 line (admittedly only about 20-30 chars long) .txt file seemed to go very quickly for a small number of searchwords, which has pleased me.
However, I realised I've had more problems parsing a file containing only, say, 1,000 lines, primarily due to the amount processing done to each line, and the script eventually timing out. With my new system (that I'm working on now) I plan to searh first and only process further the lines (in other words, the database entries) which matched the search. However, I'm worried this may still timeout on some searches. Is there anyway we can change the timeout limit, or is it a server only thing? If not, would using 'print "Location:..."' to point to another script to move from the searching to the processing cause the timeout counter to reset? Or does the timer continue until a page is fully downloaded and displayed?
Cheers,
Rikki
However, I realised I've had more problems parsing a file containing only, say, 1,000 lines, primarily due to the amount processing done to each line, and the script eventually timing out. With my new system (that I'm working on now) I plan to searh first and only process further the lines (in other words, the database entries) which matched the search. However, I'm worried this may still timeout on some searches. Is there anyway we can change the timeout limit, or is it a server only thing? If not, would using 'print "Location:..."' to point to another script to move from the searching to the processing cause the timeout counter to reset? Or does the timer continue until a page is fully downloaded and displayed?
Cheers,
Rikki
There have been no replies to this thread yet.
I have done some testing on searching through largish flat file databases, and although it was rather crude and contained repeating data, searching through a 10,000 line (admittedly only about 20-30 chars long) .txt file seemed to go very quickly for a small number of searchwords, which has pleased me.
However, I realised I've had more problems parsing a file containing only, say, 1,000 lines, primarily due to the amount processing done to each line, and the script eventually timing out. With my new system (that I'm working on now) I plan to searh first and only process further the lines (in other words, the database entries) which matched the search. However, I'm worried this may still timeout on some searches. Is there anyway we can change the timeout limit, or is it a server only thing? If not, would using 'print "Location:..."' to point to another script to move from the searching to the processing cause the timeout counter to reset? Or does the timer continue until a page is fully downloaded and displayed?
Cheers,
Rikki
However, I realised I've had more problems parsing a file containing only, say, 1,000 lines, primarily due to the amount processing done to each line, and the script eventually timing out. With my new system (that I'm working on now) I plan to searh first and only process further the lines (in other words, the database entries) which matched the search. However, I'm worried this may still timeout on some searches. Is there anyway we can change the timeout limit, or is it a server only thing? If not, would using 'print "Location:..."' to point to another script to move from the searching to the processing cause the timeout counter to reset? Or does the timer continue until a page is fully downloaded and displayed?
Cheers,
Rikki