[syslog-ng] [Bug 23] MySQL default configuration causes error on 'pid' column

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Mon Sep 29 11:46:56 CEST 2008


Balazs Scheidler <bazsi at balabit.hu> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

--- Comment #8 from Balazs Scheidler <bazsi at balabit.hu>  2008-09-29 11:46:56 ---
(In reply to comment #7)
> > in text-based fields the empty strings should be '' instead of NULL.
> Well, yes and no.  Empty strings should be '', but MISSING strings should be NULL.  Ideally, missing anything should become a NULL value, at least for the
> purposes of database insertion.  Unfortunately it's not that simple.
> But it illustrates a core problem with the current DB interface.  Everything is being treated as a string in the INSERT statement and there is no way to
> differentiate between an empty string value and a missing data value.

true, syslog-ng provides the flexibility to use templates in column values, I think that's pretty nifty, but yes, this means that all columns are 
treated as strings.

as almost everything is a string in a log message, I find this limitation not that severe.

> I have tested the patch and it didn't work.  A missing PID still produces an empty string in the INSERT statement.

hmm.. you're right, I used a construct that does not yet work in 2.1.

I revert the patch, as it causes breakage and REOPEN this bug report.

Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the syslog-ng mailing list