The delete operation does not sound correct at the beginning of the pipeline. Stages in the pipeline are supposed to pass rows around. I would say that switching to single thread execution will fix the problem, but just as a side effect. Why not performing the delete as the first task inside the write operation?
On Thu, Apr 14, 2011 at 17:50, Ryan <[email protected]> wrote: > I have a very simple Etl Process object that performs 3 operations: > * Delete (clear target table) > * Select > * Write > > These have always run in order. However, last night we had a problem > where the delete occured last, obviously very problematic. Is the > answer as simple as using a SingleThreadedPipelineExecuter? > > Public Class MainProcess > Inherits EtlProcess > Implements IProcess > > Protected Overrides Sub Initialize() > > ' Should I add this line? > ' Me.PipelineExecuter = New > SingleThreadedPipelineExecuter() > > Register(New DeleteTarget(_targetConnSettings)) > > Register(New ReadFromSource(_sourceConnSettings)) > > Register(New WriteToTarget(_targetConnSettings, > TARGET_TABLE_NAME)) > > End Sub > > Public Sub Start() Implements IProcess.Start > MyBase.Execute() > End Sub > End Class > > -- > 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. > > -- 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.
