Release: mod_log_sql v 1.96

Edward Rudd <[email protected]> Thu, 04 Mar 2004 19:04:59 -0600
Newsgroups gmane.comp.apache.mod-log-sql
Organization Omegaware Systems Ltd.
Message-ID <[email protected]>
mod_log_sql users,

I'm pleased to announce mod_log_sql version 1.96.
This is the *developmental* branch of mod_log_sql, but the only one
supporting Apache 2.0. I am making great progress toward an official
stable release.. This new version has many changes, so I urge you to
test this release thoroughly and report any issues to the mailing list
or to me, the new maintainer of mod_log_sql.

The currently the official source for mod_log_sql is
http://www.outoforder.cc/projects/apache/mod_log_sql/. And the mailing
list will be moving hopefully in a week or two, after I evaluate mailing
list software options and setup the service. Any suggestions for mailing
list software is welcome.

Now for the changes to mod_log_sql,
* Bugfix where LogSQLPreserveFile configuration option didn't work.
* Bugfix where LogSQLMassVirtualhosting didn't work anymore.
* A new configuration directive "LogSQLDBParam" has now been added to
ease the adding of new database specific configuration options. This
configuration directive replaces LogSQLTcpPort, LogSQLDatabase, and
LogSQLSocketFile. Use of the old configuration directives is deprecated,
and they will most likely be removed from newer releases of mod_log_sql.
Examples.
  LogSQLDBParam database loggingdb
  LogSQLDBParam tcpport 3306
  LogSQLDBParam socketfile /var/lib/mysql/mysql.sock
the configuration name (first argument) is currently case sensitive (nex
release will fix that).
* The mysql code has been separated out to a separate code module, and
the next release will offer (hopefully) DBI and PostgreSQL support. if
anyone would like to write these extensions for me look at the
mod_log_sql_mysql.c and follow the function prototypes in there.
* Documentation is back and updated.. And in Docbook format. Please read
through the documentation and offer any updates, especially platform
specific notes to compiling.
* notes, cookies, headersin, and headersout tables are no longer created
unless they are used (no more cluttering up the DB with unused tables).

TODO/Future versions:
Here are some ideas I have as I work toward the stable 2.0 release.
* LogSQLLoginInfo using a mysql://username:password@host/databse style
syntax.
* updated LogSQLTransferLogFormat using full names of logging types
instead of character codes.. ie.
  LogSQLTransferLogFormat timestamp request_uri bytes_sent
* Adding +/- flags to these directive:  LogSQLRequestAccept,
LogSQLRequestIgnore, LogSQLRemhostIgnore, LogSQlWhichCookies,
LogSQLWhichHeadersIn, LogSQLWhichHeadersOut, LogSQLWhichNotes,
LogSQLTransferLogFormat.  Allowing one to specify a default policy in
the global configuration and then Add or Subtract in virutual hosts..ie.
  LogSQLWhichCookies trackingcooke someothercookie
  <Virtualhost myhost:80>
  LogSQLWhichCookies -someothercookie, +mycookie
  </VirtualHost>

Let me know your thoughts on these new ideas, and of current
implementations.. And of course report bugs if you find them.
Regards,
Edward Rudd
-- 
Edward Rudd <[email protected]>
Website http://outoforder.cc/