You might be better off looking at $r->servername in a PerlPostReadRequest handler or something similar, and then setting the db connect value in $r->pnotes so that you don't pollute ENV across all requests.
Even better, run a separate apache server for qa. If you get a bug in there, you run the risk of connecting your qa site to the production database, which can have undesirable consequences. This approach also has the added bonus that you will be able to use Apache::DBI for persistent DB connections, whereas I don't think you can do that with the example you have shown.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
