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

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Thu Sep 25 05:21:53 CEST 2008


https://bugzilla.balabit.com/show_bug.cgi?id=23





--- Comment #4 from Mark LaCroix <mark at la-croix.net>  2008-09-25 05:21:54 ---
I'm not following you on this one.

The default SQL destination uses MySQL and sets the PID column as INT.  It is possible to send an empty string when the PID is not set however and this causes
an error in MySQL 5.0.  I believe there should be a solution for this.

The easiest thing to do would be to change the PID column to VARCHAR, but I think there is some room for improvement in the underlying code.  Currently when a
value (PID in this case) is not set, it gets defaulted to an empty string.  If it were set to NULL however, the database backend could properly process the
query.  This way, a user could set up the PID column to be "int not null default 0".  When the NULL value tries to get inserted, it would default to the proper
value of 0.


-- 
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