Judging by the number of Ruby on Rails developpers asking themselves this question,
this is the missing example of Rails. (It's not in my Rails reference book, and I've never seen any example on any blog.)

One solution is to create a new model for the association. It schould be the case
if you add attributes to the association (because push_with_attributes is now deprecated).
You can then simply find the association given the ids of your linked object and call destroy.

However, when you don't have any attribute in your liaison, the has_and_belongs_to_many
is nicer to work with. (you don't need a rails model for the liaison.)
Here is a link to the methods has_and_belongs_to_many adds where we can read :

"collection.delete(object, …) - removes one or more objects from the 
collection by removing their associations from the join table.
This does not destroy the objects."

Let's assume we dispose of 2 models 'Post' and 'Category' with a N-N association :

class Post < ActiveRecord::Base
  has_and_belongs_to_many :categories
end

class Category < ActiveRecord::Base
  has_and_belongs_to_many :posts
end

To delete an association (remove a post from a category) you can use this method :

  def remove_post_from_category
     post = Post.find(params[:post][:id])
     category = post.categories.find(params[:category][:id])

     if category
        post.categories.delete(category)
     end

  end

This function will destroy the association but won't destroy the category.

You can also removes all the categories from the posts by using :

collection.clear - removes every object from the collection. 
This does not destroy the objects.

In our example :

 
post.categories.clear

Every time your browser loads an new url, it also request a file called 'favicon.ico' in the same subdirectory. This generates a LOT of errors in the Ruby on Rails logs of my app.

One way to avoid those errors is to redirect the browser to the root /favicon.ico file.
Just add this line in the /public/.htaccess file of your rails project :

 RewriteRule ^(.*)favicon.ico$ favicon.ico [QSA]

Do you use another method to resolve this problem ?

1. The first way uses has_and_belongs_to_many in both models. You'll have to create a join table that has no corresponding model or primary key. ( ActiveRecord will look by default for a join table called groups_users )
class Group < ActiveRecord::Base has_and_belongs_to_many :users # foreign keys in the join table end class User < ActiveRecord::Base has_and_belongs_to_many :groups # foreign keys in the join table end The join table can have more attributes which can be filled with the push_with_attributes method: class User < ActiveRecord::Base has_and_belongs_to_many :groups # foreign keys in the join table def join_group(group) groups.push_with_attributes(group, :joined_at => Time.now) end end
2. The second way uses a has_many association with the :through option and a join model: class Subscriptions < ActiveRecord::Base belongs_to :group # foreign key - programmer_id belongs_to :user # foreign key - project_id end class Group < ActiveRecord::Base has_many :subscriptions has_many :users, :through => :subscriptions end class User < ActiveRecord::Base has_many :subscriptions has_many :groups, :through => :subscriptions end