-
Notifications
You must be signed in to change notification settings - Fork 878
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
Status of has_many through? #369
Comments
Yes it's planned but not implemented yet. In the mean time you could try using the code from pull request #345, which apparently works in some capacity. |
Where is it documented? I mean how to utilise it? |
You'd have to talk to the author, @lyfeyaj. |
Ok. I take it that pull doesn't include the order_by_primary_key branch's changes? I rely on those. Hmmm. |
Sorry, I'm trying to merge |
Don't be sorry. It's all great work. I wouldn't stand a chance at creating half the site I want without gems like this. |
I've read all I can find here about using paper_trail with "has_many through" associations. Am I right in thinking greater support is intended for some time but hasn't been implemented yet?
I have a model with three associated models, all using join tables. I have a history page for the model that shows each revision. Ideally I want to be able to present changes made to join tables alongside changes made to the main model AND have the revert action revert them as well.
From what I read here that sounds either impossible or beyond my coding skill. Would I be better off trying to list changes to the join tables separately but on the same history page? So that you can revert them too but not with the same action?
If what I want ideally is possible then I will try and do the work but if it's impossible currently I'll try this less ideal but probably functioning way of doing it.
The text was updated successfully, but these errors were encountered: