I am discovering that HABTM has some issues in AS -- or I have some issues trying to use it the way it was designed.
Traditionally Rail's HABTM has no extra attributes and equally no id. For the sake of completeness, I created join tables for my many-to- many relationships. However, Rails and HABTM, when it encounters an actual join table, overrrides the ID which violates the PRIMARY KEY. However, the advantage of HABTM within AS is its support for bi- directional editing -- which is what I want. While HAS_MANY with :through works for showing, it does not support editing -- namely, it is read_only. I tried the suggestion at http://groups.google.com/group/activescaffold/browse_thread/thread/b336a53852b947a1/6b72474f6165f087?lnk=gst&q=student+subject#6b72474f6165f087 but it did not work. Suggestions? I am happy to override the controllers update/create/delete methods, but they complain of missing views. Maybe I am doing something wrong? Alternatively, should I override methods on the model? And if so, which ones? Filters such as after_create? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/activescaffold?hl=en -~----------~----~----~----~------~----~------~--~---
