comment on

My Log4perl chops are extremely stale at this point. My question would be, is it properly the logger’s responsibility? Log4perl can send email and such too but you would never expect it to configure/start sendmail as a part of normal “just in time” operations. I think the application consuming the logger should be responsible for setting up the DB. That said, this might do it. See also: Log::Log4perl::FAQ. Completely untested–

log4perl.appender.app_db.datasource = sub { \
   require DBI; \
   my $connect_info = "dbi:SQLite:uri=file:log4perl.sqlite"; \
   my $dbh = DBI->connect($connect_info); \
   # ERROR handling, possible DB    creation left out! \
   $dbh->do(<<"_SQL_"); \
       CREATE TABLE IF NOT EXISTS log (    \
             # ... table definition    .... \
       ); \
_SQL_ \
   $connect_info; \
}
[download]

In reply to Re^3: Log4perl: Create missing SQLite file and log to it by Your Mother
in thread Log4perl: Create missing SQLite file and log to it by mbloecker

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.


XP is just a number
	PerlMonks