in reply to Parsing user input into CSV table

If all you want to store are these HTML pages, why dump them in CSV files? It's bound to mess up ;-) IMHO, you'd better just dump the HTML pages in seperate files. That would probably be faster too.

I'm not sure what you mean with "how to parse the user input" since you've already stated you're using the CGI module. Do you want to strip certain tags? Validate the HTML before you dump it to your harddisk?

--
b10m

All code is usually tested, but rarely trusted.

Replies are listed 'Best First'.
Re: Re: Parsing user input into CSV table
by lwicks (Friar) on Apr 14, 2004 at 10:17 UTC
    Basically the HTML is a small part of a larger whole.
    The idea of storing in separate files might work, but ideally would like to keep everything in a single storage format.

    The CSV format is because this is for use on a bog standard webserver, minus a SQL server and such like. The use here is that HTML is pasted/typed into a textarea box on a webform, (along with some other info) and is stored in the table.
    The table is then queried and used to produce firstly a list of pages and then upon clicking on a link, they are displayed a web page with the HTML.

    Kind of a CMS, mainly a get the design away from the infrastructure kinda thing. The people who will be typing the data will start by writing plain text, which would then have html tags added afterwards.

    Commas are the killer at themoment obviously :-)

    Kia Kaha, Kia Toa, Kia Manawanui!
    Be Strong, Be Brave, Be perservering!
[reply]

In Section Seekers of Perl Wisdom