in reply to Max Submissions?

If you cannot afford DataBasing the entries, I really think you should put the entries into a seperate flat text file, and then retrieve them upon request. This way you won't have a lot of html files to take care of, just a template file and the rest of the data databased.

Now, using simple methods you can count your way through the text file and print the results, showing 1 - 10 - or even 100 entry per page.

If you don't know what I'm talking about: here's some explanation:
You have a template html file and you know where to print the results.
You open the text file and get the entries you want and then print them out.
now, whenever you need to change the look of the page, you have only one html file to change that does all the rest.

I hope this helps you decide.

He who asks will be a fool for five minutes, but he who doesn't ask will remain a fool for life.

Chady | http://chady.net/

Replies are listed 'Best First'.
Re: Max Submissions?
by ducky (Scribe) on Sep 06, 2001 at 21:36 UTC

    Building on the idea of flat files, one might be inclined to use DBD::CSV where a flat file gets the DBI treatment. I use this on hosts where I can't install a full database, but I need simple database access lest I be forced to code it all myself.

    Of course, moving from an HTML file to flat files isn't trivial if you're knee deep in data already, but the transition would easily pay for itself when the entries gets into the 1000s and you need to go to a full database solution because (suprise!) the client side is already done! Just change the dbd connect statement at the top to point to oracle, postgres, mysql, what-have-you, let out an evil cackle or two, then go to your next project =)

    -Ducky

[reply]

In Section Seekers of Perl Wisdom