Fix associations with per-class/multiple database connections #3732
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current ActiveRecord does not work with per class database connections. It worked with 2.x and 3.0 series.
Here is a simple example, running against the ActiveRecord test database: https://gist.github.com/1388725
It throws ActiveRecord::ConnectionNotEstablished in line 16 without this patch.
The patch applies cleanly to 3-1-stable and master. I verified, that all ActiveRecord tests pass on SQLite and PostgreSQL.