#3190 HABTM no longer works when using multiple databases - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#3190 ✓duplicate

HABTM no longer works when using multiple databases

Reported by sds | September 11th, 2009 @ 11:03 AM

The check has_primary_key? in has_and_belongs_to_many_association.rb fails when using multiple databases because it uses ActiveRecord::Base's connection and not the correct connection for the association.

This change changes it to use the @owner connection.

This first broke on this commit
http://github.com/rails/rails/commit/9c1bac0b7fcb627640db6824dca3e6...
- which was removed by commit http://github.com/rails/rails/commit/594a281d663dd8a7801651f4aea7e5... - but was again added by this commit http://github.com/rails/rails/commit/2b82708b0efb3a3458e8177beab58f...

I enclose a patch to fix it.

habtm_fix.diff 1.2 KB

Comments and changes to this ticket

José Valim September 11th, 2009 @ 09:04 PM
Actually, I think we should remove the code all together. The feature is great, but the implementation is very slow. My patch attemps to solve it, but fails in Postgres for a strange reason.
Jeremy Kemper September 11th, 2009 @ 10:10 PM
- State changed from “new” to “duplicate”
sds, could you attach the patch to ticket #3128?
You flagged this item as spam.
erzapito October 16th, 2009 @ 11:46 AM
the delete_records method also fails:

line 90 is:
@c.delete(sql)

and should be:
@owner.connection.delete(sql)