<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#0050d0">
Sent: Mon Jan 24 2011 04:12:37 GMT-0700 (Mountain Standard Time)<br>
From: Balazs Scheidler <a class="moz-txt-link-rfc2396E" href="mailto:bazsi@balabit.hu"><bazsi@balabit.hu></a><br>
To: Syslog-ng users' and developers' mailing list
<a class="moz-txt-link-rfc2396E" href="mailto:syslog-ng@lists.balabit.hu"><syslog-ng@lists.balabit.hu></a> <br>
Subject: Re: [syslog-ng] abandon libdbi and write a new sql driver?
<blockquote cite="mid:1295867557.6668.22.camel@bzorp.lan" type="cite">
<pre wrap="">On Thu, 2011-01-20 at 13:17 -0700, Patrick H. wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Reading through the mailing list lately I've seen a fair amount of
problems reported with libdbi. Given that it also doesnt support
prepared statements which is a very important feature, I'm wondering
if libdbi should just be dropped entirely. Libdbi seems to be of use
to applications that want just very basic sql support, and not for
anything involving high performance or reliability.
I know its no small undertaking to write a new DBI for all the common
databases out there, but if syslog-ng is supposed to be
high-performing, libdbi does not fit in with that. I dont know if it'd
be best to start a new project to replace libdbi but accomplish the
same thing of providing a common API for all databases, or to just
write separate modules for syslog-ng 3.2+ for each database out there.
Writing modules would certainly be easier as they could be written
independently by people who best know each database API.
This is all just my opinion, but I for one am all for it. In my
production environment, we do logging to a database, and libdbi just
didnt have the flexibility or performance we needed, so I ended up
writing a separate program which connects to the database to perform
the inserts. Would be nice to avoid having to do that.
I know I've also heard many recommendations of piping out to a perl
script to do the inserts. A perl script should never do its job faster
than C code.
</pre>
</blockquote>
<pre wrap=""><!---->
Honestly I was thinking about forking libdbi/libdbi-drivers as we do
have a couple of changes and upstream is not really doing regular
releases. And that's the key problem. libdbi is basically stalled as a
project and without them releasing bugfixes is causing us and our users
pain.
But I don't see anything against libdbi per-se, within syslog-ng a
similar API would be needed to cover all database APIs, so why reinvent
the wheel?
</pre>
</blockquote>
Well thats certainly an option. I just remember looking at the code
once and it wasnt very clean. But that was something like a year ago
and I may be remembering some other project I looked at. Primarily I
just didnt think libdbi in its current state is in line with what
syslog-ng is trying to accomplish. How that gets resolved isnt that
important.<br>
<br>
I know I would love to have a mature common database API I could use in
some of my other projects :-P<br>
<br>
-Patrick<br>
</body>
</html>