We're just starting to use RhinoETL to do some data analysis. Some of the team were wondering why all operations have to take in a Row and return a Row rather than doing something with generics so it would be possible to pass data objects through the system.
Was it just a matter of keeping the interfaces simple? Was it a performance thing so there's not so much time spent marshaling values between objects? Does it just lend itself to writing data manipulations that simple? I think our main problem is that it feels a bit strange to be using data structures so similar to data sets and data tables after moving away from that in our web application code. Does anyone know why it's designed this way? -- 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.
