> All of the above suggestions may be valid, however it does not explain
> how, once the OP has managed by fair means or foul to get hold of the
> member object that it manages to mutate between his two uses of it.
OK. I want to jump back in here to make sure that Bill doesn't think
that he did offend me with his comments. He definitely did not. I
welcome all of the help that I can get and Bill's comments are not
only valid but contain a lot of help. None the less, I also agree
with you, Colin, in that Bill's comments really offer no explanation
as to how the object manages to mutate between the two uses of it.
What I'm trying to do at the moment is to clean things up by following
Bill's suggestions. It's much easier to troubleshoot in the
controller than it is in the view. I expect that by using that
approach I will ultimately get things to work as desired.
Unfortunately, the downside of that approach is that I may never
understand why my code (bad as it may have been) didn't work. That's
a bit unsettling. Anyway, I continue to work on this issue. I will
report back to the list once I have something to report. As always,
thanks to all for the help.
... doug
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
