There was a discussion in 2008 about adding branching on error functionality to Rhino.Et, Rhino.Etl error collection: part two<../d/topic/rhino-tools-dev/GElfdwF5eCA/discussion>.
I was wondering if this functionatly was added along the lines that Ayende proposed in the discussion: From: [email protected] To: [email protected] Subject: [rhino-tools-dev] Re: Rhino.Etl error collection: part two Here is the deal, are we talking about just gather information to be process at a at a later date, or are we talking about branching the pipeline? Are we talking about this process: operation hasErrors: for row in rows: to_error row if row.HasErrors process row unless row.HasErrors process test: get_data() hasErrors() for errorRow in errorRows: output_to_file errorRow Or something like this: branch splitOnError: for row in rows: send_row row, "error" if row.HasErrors send_row row unless row.HasErrors operation logErrors: output_to_file row for row in rows process test: get_data() splitOnError: normal: process_data() error: logErrors() Thanks Michael -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To view this discussion on the web visit https://groups.google.com/d/msg/rhino-tools-dev/-/_ChJOj3WenYJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
