[syslog-ng] CSV parser and empty fields

[Balazs Scheidler]

On Fri, 2010-11-05 at 16:40 -0700, Matthew Hall wrote:
> I'm surprised it doesn't handle doubled delimiters right.
> 
> However I am likewise stumped. I can't find any explanation anywhere in 
> the Balabit docs which explain what escape-* options do specifically.
> 
> I guess reading the code is the only option for now. :/

Robert has started adding this info into the docs, but here's a short
explanation:

escape-none: quotes cannot happen within the value as no escaping is
defined. the end of a field is the next closing quote character. 

escape-backslash: any character can be escaped within the value with the
backslash character, e.g. "alma\"fa" is equal to the value alma"fa

escape-double-char: quote characters can be escaped by doubling them,
with the previous example the field "alma""fa" is equal to the value
alma"fa

> 
> On Fri, Nov 05, 2010 at 05:26:38PM -0600, Bill Anderson wrote:
> > Thanks for your reply, Mathew. Perhaps I wasn't clear enough. The 
> > syslog-ng produced logfile that logs $MSG is *just fine*. The tabs are 
> > there, and anything that parses it and expects the fields gets them 
> > just fine. The problem arises when the template only needs to log 
> > fields from the csv parser and a preceding field is empty. If there 
> > are any flags on that page that affect how the csv-parser handles 
> > empty fields, I'd appreciate them being pointed out, as I didn't see 
> > any.
> > 
> > Cheers,
> > Bill
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.campin.net/syslog-ng/faq.html
> 
> 

-- 
Bazsi