Applied, thans. On Sun, Jan 18, 2009 at 8:50 PM, Simone Busoli <[email protected]>wrote:
> Sorry, here it is. > > > On Mon, Jan 19, 2009 at 2:46 AM, Ayende Rahien <[email protected]> wrote: > >> It is missing SingleRowEventRaisingEnumerator >> >> >> On Sun, Jan 18, 2009 at 1:56 PM, Simone Busoli >> <[email protected]>wrote: >> >>> Here's a patch with tests. >>> >>> On Sun, Jan 18, 2009 at 7:53 PM, Simone Busoli >>> <[email protected]>wrote: >>> >>>> Thanks, I'll do that. >>>> >>>> >>>> On Sun, Jan 18, 2009 at 7:51 PM, Ayende Rahien <[email protected]>wrote: >>>> >>>>> No, I just didn't have the chance to write any ETL type tasks.Rhino >>>>> ETL is still my tool of choice for that. >>>>> >>>>> It is just that I am afraid that I don't remember much of the actual >>>>> internal behavior. >>>>> >>>>> I can recommend that you would use the single threaded pipeline and try >>>>> to walk through it, tough. >>>>> >>>>> >>>>> On Sun, Jan 18, 2009 at 1:48 PM, Simone Busoli < >>>>> [email protected]> wrote: >>>>> >>>>>> May I ask you if you choose for another tool to perform ETL >>>>>> operations? I'm encountering the same issues with DTS and SSIS you >>>>>> probably >>>>>> had when you wrote RhinoETL, and looking for alternatives. I admit >>>>>> that I found it very useful so far, after writing our own DSL in ruby to >>>>>> deal with DTS. >>>>>> >>>>>> >>>>>> On Sun, Jan 18, 2009 at 7:44 PM, Ayende Rahien <[email protected]>wrote: >>>>>> >>>>>>> Haven't done much with Rhino ETL for about a year, I am afraid. >>>>>>> >>>>>>> >>>>>>> On Sun, Jan 18, 2009 at 1:41 PM, Simone Busoli < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi, I'm trying out RhinoETL and I'm having some issues in trying to >>>>>>>> wrap my head around how the EventRaisingEnumerator is >>>>>>>> used.Specifically, I want to log the numbers of row processed during >>>>>>>> the >>>>>>>> operation, and I'm trying to do so with this code: >>>>>>>> >>>>>>>> public DeleteData(string connectionStringName) : >>>>>>>> base(connectionStringName) >>>>>>>> { >>>>>>>> OnRowProcessed += delegate >>>>>>>> { >>>>>>>> rowsDeleted++; >>>>>>>> }); >>>>>>>> OnFinishedProcessing += op => >>>>>>>> { >>>>>>>> Info("Rows deleted: {0}", rowsDeleted); >>>>>>>> }; >>>>>>>> } >>>>>>>> >>>>>>>> where DeleteData inherits from OutputCommandOperation. With the code >>>>>>>> that's on the trunk only the OnFinishedProcessingEvent is raised, >>>>>>>> therefore >>>>>>>> 0 is always logged, printing this out: >>>>>>>> >>>>>>>> Committing DeleteData >>>>>>>> Committed DeleteData >>>>>>>> Rows deleted: 0 >>>>>>>> >>>>>>>> I tried by modifying the OutputCommandOperation class by wrapping >>>>>>>> the rows in the Execute method in an EventRaisingEnumerator, but doing >>>>>>>> so I >>>>>>>> get this: >>>>>>>> >>>>>>>> Rows deleted: x >>>>>>>> Committing DeleteData >>>>>>>> Committed DeleteData >>>>>>>> Rows deleted: x >>>>>>>> >>>>>>>> Ideally, I'd want the Rows deleted message once after the commit >>>>>>>> message, but I think this might be tricky, since I guess the >>>>>>>> processing is >>>>>>>> already wrapped in an EventRaisingEnumerable, just not in the point I >>>>>>>> would >>>>>>>> like it. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. 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 -~----------~----~----~----~------~----~------~--~---
