Java The Hutt

Yesterday while trying to model some domain objects that need to be involved in a many-many relationship I ran into a problem where AR doesn't work with model objects that are using single table inheritance. How about an example of just what I'm talking about...
(These aren't the real domain model objects so don't pan me for bad design.)

def Band < ActiveRecord::Base
  has_and_belongs_to_many :fans
end

def RedHotChiliPeppers < Band
end

def Fan < ActiveRecord::Base
  has_and_belongs_to_many :bands
end

OK so that's the class structure let's fire up the console and create some objects:

>> fan = Fan.new
>> band = RedHotChiliPeppers.new
>> fan.bands
=> []
>> fan.bands<< band
ActiveRecord::AssociationTypeMismatch: Band expected, got RedHotChiliPeppers
        from /usr/local/ror/lib/ruby/gems/1.8/gems/activerecord-1.14.1/lib/active_record/associations/association_proxy.rb:134:in `raise_on_type_mismatch'
        from /usr/local/ror/lib/ruby/gems/1.8/gems/activerecord-1.14.1/lib/active_record/associations/association_collection.rb:24:in `<<'
        from /usr/local/ror/lib/ruby/gems/1.8/gems/activerecord-1.14.1/lib/active_record/associations/association_collection.rb:23:in `<<'
        from /usr/local/ror/lib/ruby/gems/1.8/gems/activerecord-1.14.1/lib/active_record/connection_adapters/abstract/database_statements.rb:51:in `transaction'
        from /usr/local/ror/lib/ruby/gems/1.8/gems/activerecord-1.14.1/lib/active_record/transactions.rb:91:in `transaction'
        from /usr/local/ror/lib/ruby/gems/1.8/gems/activerecord-1.14.1/lib/active_record/transactions.rb:118:in `transaction'
        from /usr/local/ror/lib/ruby/gems/1.8/gems/activerecord-1.14.1/lib/active_record/associations/association_collection.rb:22:in `<<'
        from (irb):33

I've been told that there's a patch that's pending release to fix this problem but in the meantime I've worked around this by moving the HABTM relationship from Band into the RedHotChiliPeppers subclass. I only have one other subclass of Band in my model so it's not too terrible to deal with having that relationship in both of those subclasses but this AR bug should be fixed.

A search through the bug database didn't find this particular bug but others that are closely related:

http://dev.rubyonrails.org/search?q=has_and_belongs_to_many+inheritance&ticket=on&changeset=on

As a result I filed a ticket for this:
http://dev.rubyonrails.org/ticket/5425

I'm not on edge rails (I'm using 1.1.2) so maybe this is fixed by now, guess we'll see by the activity on the ticket.