Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

I agree with the previous posts, and I just wanted to point out something more.

When dealing with CGIs and text file databases, locking is highly recommended, because of the nature of HTTP requests themselves.

You should also consider users pressing submitting many times or reloading the page, they both impact negatively your flat file DB in case operations that change data are involved.

I personally like to use text files when it makes sense, e.g. when data needs to be implicitly human readable or when dealing with pre-existing databases and file formats.

In other situations I tend to prefer DBM files, woinderfully supported by perl (e.g. MLDBM) and interoperable as well, or the DBI interface, which can operate on text files when/if needed, as already pointed out.

-- TMTOWTDI


In reply to Re: perl cgi and flat textfile by trantor
in thread perl cgi and flat textfile by kiat

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.