Are you sure about the flat-file approach? That way you always have to read/write the whole thing when editing a single item like: 
#!/usr/bin/perl -i

#first arg is the item_number, second the text-file with replacement
#dbase file on STDIN, edited file on STDOUT

my $item_number = $ARGV[0];
open IN, $ARGV[1] or die "Could not open $ARGV[1]: $!";
my $replacement;
{
  local $/ = undef;
  $replacement = <IN>;
}

{ 
  local $/ = '::';
  while( <> ) {
    $_ = $replacement if $. == $item_number;
    print;
    print '::' if not eof;
  }
}

[download]
When the dbase gets large, the overhead may become problematic. Consider a RDBM like postgres or a good DB like BerkeleyDB.

Cheers,

Jeroen
"We are not alone"(FZ)

In reply to Re: delimiters anyone?? by jeroenes
in thread delimiters anyone?? by deriwana

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.