On Fri, 2007-11-16 at 10:38 -0800, Evan Rempel wrote:
Balazs Scheidler wrote:
On Mon, 2007-10-01 at 11:27 -0700, Evan Rempel wrote:
Balazs Scheidler wrote:
Only the PE version of syslog-ng has direct database connectivity in which case you need libdbi8. Was there consideration of database access using ODBC? If there was, could you provide a couple of reasons (rational or otherwise) why ODBC was not implimented?
Not really. I did not even consider ODBC as I felt it was too complicated for my case, and my perception was that ODBC is not that well supported on Linux/UNIX.
Because of your email I've googled a bit, and I've found unixodbc, which seems to do the trick, however it seems inherently more complex than libdbi. (and some of the drivers cost extra money)
Do you have any specific advantage in mind regarding libdbi vs. ODBC?
From my perspective I like the odbc approach better because the odbc drivers are generally written by the database vendor/author rather than an third party. Someone else would have to correct me, but I don't think any database group writes their own dbi drivers. This seems like it would result in a more stable environment, and that's what I want in my logging.
The whole things comes to a confusing mess when you think of the dbiodbc which is an odbc driver for the dbi API which would then allow you to use any odbc driver you wish. Of course the same is true in reverse, you can get an odbcdbi which provides and dbi driver with an odbc interface.
True enough, I've already ran into problems with the Oracle DBI driver. For now it works, we support our own libdbi/dbd packages, but the end result might be that we migrate to using ODBC in the future. -- Bazsi