I was in the field for years before I realized that my system admin code (grep, awk, cut, on flat files) qualified as 'database' work. Thus, even if this isn't strictly a valid Perlish question, I don't think that the question is inherently bad.

Note: This may have something to do with the fact that half of my posts might be invalidated if we insisted that I actually provide technical insight on everything I say. :)

In any event, if you treat a flat file as a database table, each line of input becomes a database "row." In that context, you can identify "fields" in that table by their relative position in the line (fixed width), or by split /x/ on some character (delimited). If you sysread() your data, I guess you could treat it as binary. Does anyone do this any more? I don't think I've done it since I worked (in C) under VAX/VMS, and it's mostly been supplanted in the database world by BLOBs (binary large objects).

Having now said this, if you are trying to get a database job that isn't entry level, you're probably overmatched (as Fletch has stated). But that said, I never object to people wanting to grow in knowledge. If you show a willingness to make the effort to learn, it may just get you where you want to be.

In reply to Re^2: Slightly OT MySQL question by papidave
in thread Slightly OT MySQL question by Anonymous Monk

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.