Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why do you not support Custom Object Changes settings by model? #1501

Open
kindtiger95 opened this issue Dec 10, 2024 · 0 comments
Open

Why do you not support Custom Object Changes settings by model? #1501

kindtiger95 opened this issue Dec 10, 2024 · 0 comments

Comments

@kindtiger95
Copy link

kindtiger95 commented Dec 10, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant