Frederick Cheung wrote: > for a normal HABTM there is no corresponding model, so rows never get > updated by this code path. The habtm association generates sql > fragments directly and runs them > Furthermore, because habtm is usually used as a 'dumb' join table, > it's only ever a question of deleting or inserting rows > > Fred
Enlightenment is a slow process, at least for me. So I think what's going on is that I've created a table that *should* be declared as HABTM. And now that I think about it in those terms, I'm not sure why I didn't to that in the first place. Time for another "script/generate migration"... Thanks for your patience. - ff -- Posted via http://www.ruby-forum.com/. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
