Thanks for your reply. You're right about the efficiency not being critical here, but seeing potentially inefficient code like that always puts me on alert. As I see it, the following steps are needed:

  1. Fetch data from DB
  2. Write data into hash
  3. Loop through hash to get labels
  4. Loop through hash to get values
  5. Print HTML

With many other functions, like the pop-up menu where labels and values are the same that I showed above, you can skip steps 3 and 4 and go straight from the DB to the CGI printing. Not only that, it just feels like a lot of code! I had been hoping that there was a more concise idiom somewhere out there waiting to be discovered....

-Tats

In reply to Re: Re: Populating CGI popup_menu via DBI by Itatsumaki
in thread Populating CGI popup_menu via DBI by Itatsumaki

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.