Inheritance diagram for ODBCAppender:
Public Member Functions | |
virtual void | setOption (const String &option, const String &value) |
void | append (const spi::LoggingEventPtr &event) |
virtual void | close () |
void | flushBuffer () |
virtual bool | requiresLayout () const |
void | setSql (const String &s) |
const String & | getSql () const |
Protected Member Functions | |
String | getLogStatement (const spi::LoggingEventPtr &event) const |
void | execute (const String &sql) |
virtual void | closeConnection (SQLHDBC con) |
virtual SQLHDBC | getConnection () |
Protected Attributes | |
String | databaseURL |
String | databaseUser |
String | databasePassword |
SQLHDBC | connection |
String | sqlStatement |
size_t | bufferSize |
std::list< spi::LoggingEventPtr > | buffer |
The ODBCAppender provides for sending log events to a database.
Each append call adds to an ArrayList
buffer. When the buffer is filled each log event is placed in a sql statement (configurable) and executed.
BufferSize, db URL, User, & Password are configurable options in the standard log4j ways.
The setSql(String sql)
sets the SQL statement to be used for logging -- this statement is sent to a PatternLayout
(either created automaticly by the appender or added by the user). Therefore by default all the conversion patterns in PatternLayout
can be used inside of the statement. (see the test cases for examples)
Overriding the getLogStatement method allows more explicit control of the statement used for logging.
For use as a base class:
closeConnection
to handle the connection you generated. Typically this would return the connection to the pool it came from.
|
Adds the event to the buffer. When full the buffer is flushed. Implements AppenderSkeleton. |
|
Closes the appender, flushing the buffer first then closing the default connection if it is open. Implements Appender. |
|
Override this to return the connection to a pool, or to clean up the resource. The default behavior holds a single connection open until the appender is closed (typically when garbage collected). |
|
Override this to provide an alertnate method of getting connections (such as caching). One method to fix this is to open connections at the start of flushBuffer() and close them at the end. I use a connection pool outside of ODBCAppender which is accessed in an override of this method. |
|
loops through the buffer of LoggingEvents, gets a sql string from getLogStatement() and sends it to execute(). Errors are sent to the errorHandler. If a statement fails the LoggingEvent stays in the buffer! |
|
Override this to link with your connection pooling system. By default this creates a single connection which is held open until the object is garbage collected. |
|
By default getLogStatement sends the event to the required Layout object. The layout will format the given pattern into a workable SQL string. Overriding this provides direct access to the LoggingEvent when constructing the logging statement. |
|
Returns pre-formated statement eg: insert into LogTable (msg) values ("%m") |
|
ODBCAppender requires a layout. Implements Appender. |
|
Set options Reimplemented from AppenderSkeleton. |
|
Set pre-formated statement eg: insert into LogTable (msg) values ("%m") |
|
ArrayList holding the buffer of Logging Events. |
|
size of LoggingEvent buffer before writting to the database. Default is 1. |
|
Connection used by default. The connection is opened the first time it is needed and then held open until the appender is closed (usually at garbage collection). This behavior is best modified by creating a sub-class and overriding the |
|
User to use for default connection handling |
|
URL of the DB for default connection handling |
|
User to connect as for default connection handling |
|
Stores the string given to the pattern layout for conversion into a SQL statement, eg: insert into LogTable (Thread, File, Message) values ("%t", "%F", "%m") Be careful of quotes in your messages! Also see PatternLayout. |