Closed kortirso closed 1 year ago
if I understand your patch properly, its opt-out by default, so we need to specify really_destroy!(update_destroy_attributes: false)
explicitly, otherwise, it makes no difference, am I reading this right?
Also, can you update the Changelog and bump the version, please?
if I understand your patch properly, its opt-out by default, so we need to specify
really_destroy!(update_destroy_attributes: false)
explicitly, otherwise, it makes no difference, am I reading this right?Also, can you update the Changelog and bump the version, please?
yes, by default everything will work as usually, and only who wants to skip updating in the middle of really_destroy - they will call really_destroy!(update_destroy_attributes: false)
if I understand your patch properly, its opt-out by default, so we need to specify
really_destroy!(update_destroy_attributes: false)
explicitly, otherwise, it makes no difference, am I reading this right?Also, can you update the Changelog and bump the version, please?
changelog and readme are updated
@mathieujobin is it mergeable?
Thanks for the ping, looks good
released
thank you
There is issue with destroying records when, for example:
record.really_destroy!
will fail duringupdate_columns
, because record can't be saved with some nil valuesand there is some additional profit,
really_destroy!
will work faster without updating timestamps