I'm uncertain about this. There's a more general question of what operations on Tables we want to provide, vs. leaving to the user.
Currently, we have an apply! for tables that mutates the table columns in-place.
However this doesn't work when the input type can't be converted to the output type, e.g. from DateTime to Int for the hour-of-day transform. We could replace the column with the new type, but users should have a choice whether to do such a "strong" mutation.
Alternatively we could have an apply! that appends the new columns to the Table.
We could also have an apply that returns the transformed columns on their own (example), which gives users the most flexibility.
I'm uncertain about this. There's a more general question of what operations on Tables we want to provide, vs. leaving to the user.
Currently, we have an
apply!for tables that mutates the table columns in-place.However this doesn't work when the input type can't be converted to the output type, e.g. from DateTime to Int for the hour-of-day transform. We could replace the column with the new type, but users should have a choice whether to do such a "strong" mutation.
Alternatively we could have an
apply!that appends the new columns to the Table.We could also have an
applythat returns the transformed columns on their own (example), which gives users the most flexibility.