We are trying to name SQL queries in a fairly intuitive way and place them in a lib file, using SQL::Library. We have read Conway's "Perl Best Practices" as a guideline for naming subroutines. The scheme we have come up with is:

SQLCMD_Action_Object

Some examples:

  sel_count_categories,
  sel_count_clicks_agencyPage,
  sel_count_agency_visits
 = "SELECT 'Visits to detailed agency page:' as report_type, * FROM "
    . "(SELECT COUNT(*) as one_month FROM web_requests WHERE file ~* '
+rm=show_agency' AND file ~* 'agency_id=$agency_id' )

[download]

We are interested in any feedback you could give us on our approach or your suggested approach.

In reply to SQL Naming Conventions by yderkach

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.