[tcdb-devel] initializing logging

[Jason C. <jco...@vi...>]

Hey guys,

  I'm making some cool progress.  We're going to use PEAR logging mainly
because propel already does (the classes would be required anyways).
The logging will use a backtrace to determine what
file/line/function/class you called the log method from, and add that to
the log file.  It is configurable to turn off the backtrace for
performance reasons, in which case all those fields will report
'unknown'.  It also adds session id to the log line if there is one.
That way maybe we can log sessions, and have a trace of what each user
did when.

On that note I have 2 proposals to put before you tonight:

     1. We choose some special definitions for log levels that make
        sense to us.
     2. 



  I kinda want to store all configs in the database, including logging
configs.  This would make it so that the only config file we have, will
be the one generated at install time.  Everything else would be in the
database.

  Matt I know that you suggested the idea (I'm not trying to steal
credit for it).  Any objections?  I'm planning on making the database
schema such that it's like an ini file.  You have a Config object,
that's a collection of sections.  Each section can have key/value
components.  Sound like a good idea?  I'll start implementing it, tell
me to go to he@$ if you think otherwise.

Jason Corbett