Hi, I'm sorry for joining late to this party. Busy times around here.
> > I think, in our previous discussion (mailing list archive), we concluded > > that there is no value in re-trying with half of the batch. > > very possibly, I'm not remembering it. > > not doing so will simplify the code considerably, but the advantages of > retrying with half the batch are: > > 1. you deliver as much as you can > > 2. when you finally get stuck, you can pinpoint directly what message you > were stuck on (in case you have a failure based on the data, say quotes in > something that then gets formatted into a database, or slashes in > something that becomes a filename component) FYI, Oracle's OCI is able to tell you how many entries were inserted and thus you can skip the exact offending entry and retry with the next part of the batch. I suppose other DB's interfaces have the same feature, with different namings. If the output module *knows* which the bad record is, I think it's better to offload the work to the OM than to force the core to binary search for it. I'm planning to add this to omoracle, but not this week... Cheers. -- Luis Fernando Muñoz Mejías [email protected] _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
