I don't currently see the need for separate Vhost::Location objects -- the Vhost objects already have the ability to enumerate the locations they're tracking.

That indicates to me that there's already some data structure within the Vhost object that knows which locations need to be tracked. Unless there's some very compelling reason that the Locations have to be separate objects, I'd keep them as member data of the Vhost objects.

My mental image of your database schema is that you have one table for each Vhost, with location, hits, and perhaps modification time columns. If it's normalized, you might have a hosts table with a host_id, and a locations table as described before, but with a host_id which can be used to join on the hosts table.

In either case, I haven't fully answered your question yet.

I would definitely pass $dbh to the Vhost constructor. When it comes time to perform a database operation, check the definedness of it and create a new database handle if necessary.

Unless you're writing a multithreaded program, or are getting database handles from a pool (as one would expect with Apache::DBI), you won't see concurrent access on the same handle and things should work just fine.

In reply to Re: Sharing a database handle among objects by chromatic
in thread Sharing a database handle among objects by arturo

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.