You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to limited volunteers, issues that do not follow this template will be
closed without comment.
Is your feature suggestion related to a problem? Please describe.
I have encountered a situation where the size of the versions table is rapidly increasing, even though there are no changes in the MySQL JSON column. Therefore, I am considering using a custom_object_changes_adapter to track and save changes in the JSON column. However, the currently supported feature requires global configuration. Since any issues with this might propagate into a service-wide failure, I would prefer to apply the setting individually for each model.
Describe the solution you'd like to build
Change it to allow setting a custom_object_changes_adaptor for each model.
Describe alternatives you've considered
Set the object_changes_adaptor for each model in ModelConfig, and check it in Base.rb
The text was updated successfully, but these errors were encountered:
Thank you for your contribution!
Due to limited volunteers, issues that do not follow this template will be
closed without comment.
Is your feature suggestion related to a problem? Please describe.
I have encountered a situation where the size of the versions table is rapidly increasing, even though there are no changes in the MySQL JSON column. Therefore, I am considering using a custom_object_changes_adapter to track and save changes in the JSON column. However, the currently supported feature requires global configuration. Since any issues with this might propagate into a service-wide failure, I would prefer to apply the setting individually for each model.
Describe the solution you'd like to build
Change it to allow setting a custom_object_changes_adaptor for each model.
Describe alternatives you've considered
Set the object_changes_adaptor for each model in ModelConfig, and check it in Base.rb
The text was updated successfully, but these errors were encountered: