<!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: Thu Jan 20 2011 14:33:16 GMT-0700 (Mountain Standard Time)<br>
From: Matthew Hall <a class="moz-txt-link-rfc2396E" href="mailto:mhall@mhcomputing.net"><mhall@mhcomputing.net></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] Syslog-ng error
<blockquote cite="mid:20110120213316.GA8917@mhcomputing.net" type="cite">
<pre wrap="">On Thu, Jan 20, 2011 at 12:26:10PM -0700, Patrick H. wrote:
</pre>
<blockquote type="cite">
<pre wrap="">The big problem with this solution is that if the table check failed,
then inserting it will also fail. The only case this would solve is if
the user doesnt have select perms, but does have insert perms.
-Patrick
</pre>
</blockquote>
<pre wrap=""><!---->
Indeed it could be a problem but so is leaving it enabled in many cases.
Personally I find the auto-creation mostly useless and try to avoid it.
Because it won't take care of cases like special auto-incrementing ID
columns, storage engine, tablespace, and other special stuff.
So I would generally recommend making a proper table, and backing up its
schema, and storing this with a backup of the syslog-ng configuration.
Matthew.
</pre>
</blockquote>
So, make sure the table already exists and there isnt a problem :-P<br>
<br>
-Patrick<br>
</body>
</html>