What inspired this wish list request?
Tables/Update has a significant speed issue if there are multiple matching rows in the update table: Speed up Tables/Update .
Jmp can get stuck for minutes or hours while the entries from all matching rows are "added" to the main table - overwriting the previous ones - till the last one "sticks".
This comes with another disadvantage of Tables/Update: from the many rows just the last entry actually gets into the main table.
What is the improvement you would like to see?
Please add an aggregation option to Tables/Update - like the one which is already available in the Tables Query Builder Menu.
To keep Tables/Update slim, one could add just a single GUI entry (which will define the action for all added rows) .
Additionally or alternatively one can put the setting into Jmp preferences.
Default option (to reproduce the current behavior): last entry
alternative options (for non-numeric-values): mode, first entry, ...?
alternative options (for numeric values) : Median, Mean, Max, Min, ...
Why is this idea important?
With the new aggregation option, one can easily fix the speed issue of Tables/Update
- and lift the possibilities of Tables/Update close to those of Tables Query Builder.
please note:
a similar aggregation option was already proposed for virtual Joins:
aggregation option for virtual joins
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.