Replacing revisions is confusing (total replacements count) and annoying
Specifying rows/columns/custom --where expression has been a long requested feature (for more than 6 years)
Extra flexibility regarding replacements (custom PHP callback) has also been requested multiple times
Added --where flag to finely select rows aimed for replacement
Added --revision / --no-revision
Added --callback
Reroll of #104 (Dec 2018) and #128 (Sept 2019) (Feature: Call user function with --callback flag #104 )
Fix #125 (Introduce --where flag), close #142
Preliminary work for #127 (Callback access to current primary key & column)
I plea upstream to consider the PR without incurring X more extra rerolls to contributors (who already pumped dozens of hours of man work into the useless and error-prone task of rebasing) [The diff talks for itself]
This PR lack tests: Yes because tests are always hard and painful to write for external contributors but less time-consuming/easier to write correctly by long-time codebase maintainers.
Is this feature better inside (without automated tests) rather than unavaiable? I believe so.
Replacement callback & row-based filtering (include/exclude posts revisions)
--whereexpression has been a long requested feature (for more than 6 years)Added --where flag to finely select rows aimed for replacement
Added --revision / --no-revision
Added --callback
Reroll of #104 (Dec 2018) and #128 (Sept 2019) (Feature: Call user function with --callback flag #104 )
Fix #125 (Introduce
--whereflag), close #142Preliminary work for #127 (Callback access to current primary key & column)
I plea upstream to consider the PR without incurring X more extra rerolls to contributors (who already pumped dozens of hours of man work into the useless and error-prone task of rebasing) [The diff talks for itself]
This PR lack tests: Yes because tests are always hard and painful to write for external contributors but less time-consuming/easier to write correctly by long-time codebase maintainers.
Is this feature better inside (without automated tests) rather than unavaiable? I believe so.