Open Squareys opened 8 years ago
I think we have to consider the following use-cases:
Replace
, Append
, New Table
.Append
, New Table
.New Table
.New Table
.Did I miss something?
What about a Replace first option or some such (cf. Column Merger node), or a choice of which column to replace (cf. Image Calculator) for multi-column inputs?
For the K-Rows:N-Rows case above (I'm thinking of use cases similar to GroupBy), it would also be useful to have an option to append some information from the input rows, to avoid the need of a subsequent joiner. But this will probably have to be taken care of by the script developer, as it's not generalizable, right?
What about a Replace first option or some such (cf. Column Merger node), or a choice of which column to replace (cf. Image Calculator) for multi-column inputs?
I like the idea of being able to determine the column to be replaced.
For the K-Rows:N-Rows case above (I'm thinking of use cases similar to GroupBy), it would also be useful to have an option to append some information from the input rows, to avoid the need of a subsequent joiner. But this will probably have to be taken care of by the script developer, as it's not generalizable, right?
I was thinking about this a lot and I didn't find a nice solution at all, because you don't know which input row should be appended to which output-row (as the resulting output-row may depend on many input rows).
For different types of nodes we require different output settings:
@dietzc Did I miss something? :)