search for: push_attribute

...c2c_id acts_as_list :scope => :node end So basically I could have all sorts of Node types that used STI off the original Node table. And the if Foo < Node and Bar < Node I could set in Foo''s model that it HABTM Bars and at the same time order the Bars that Foo had. Now without push_attributes I can''t see how I can replicate the same thing using :through Am I going to have to use STI on NodesToNodes as well? Set up FooToBars < NodesToNodes? Any other thoughts? It was working quite well but I''d hate to have to sit and use 1.0 forever. I checked out hasmanythrough....

I''ve been using the acts_as_taggable gem in 1.0 to develop some tagging functionality. The issue is that I need to specify tags by user (i.e. update additional attributes in the join table). So, in my join table I have a "user_id" field. I''ve read about the "push_attribute" method in the api, but that doesn''t seem to work with the gem (and I''d rather not tear that apart). I''ve also been reading the tagging recipe (for Edge Rails) in Rails Recipes, but the samples don''t address how to do this. I''m having troubles i...

...s these different columns. An obvious solution is a games_players join table with a status column to contain "wanted," "played," or "favorite." However in searching online I find that, according to the rails wiki, join tables with attributes are problematic. I can use push_attributes to get that status attribute, but a delete operation would apparently kill all entries that match on the player_id and game_id columns, ignoring differences in status. Is this still an issue? Or has it been fixed in Rails 1.0? Is the usage different from what''s suggested on the wiki? (I c...