kovyrin/db-charmer — Issue #27: ":forced_slave_reads => false" doesn't work
Author: mike-ball
Created: 2011-10-13 16:06:40+00:00
State: open

We are using db-charmer 1.7.0 and Rails 3.0.7 in production.

A few of our ActiveRecord models have the following line:
db_magic :slave => :slave01, :forced_slave_reads => false

These models now use the slave db for all reads. We have to add .on_master to any queries to ensure they happen on the master. This is exactly the opposite of what the documentation says.

Setting :forced_slave_reads => false in the model should keep all reads on the master, unless we specify otherwise.

Is this a bug with the gem on Rails 3?