I'm not sure really what the problem is, actually. You seem to have a good idea of how to write this program.

I'd use the database as a repository of meta-information about the picture; in other words, I wouldn't actually store the picture data in the database, even though it *would* be possible. I'd store the actual picture file in the filesystem (somewhere in some protected directory, probably), then store the path to that file in the database. Which is exactly what you seem to be saying yourself.

For the file upload, I'd use either CGI or Apache::Request, the latter if you're using mod_perl. And I'd use DBI to communicate with the database.

Does this help? Were you looking for suggestions other than what you wrote, or more for confirmation that your idea made sense?

In reply to Re: Mysql & perl by btrott
in thread Mysql & perl by toadi

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.