Intended behaviour current_shard

[peterbrouwer]

Hi,

In version 0.8.4 octopus keeps the current_shard stored across queries, so for example in the rails console:

User.using(:my_shard).count # This will do a query on :my_shard
User.count # This will also do a query on :my_shard

In later versions (> 0.8.4) this behaviour has disappeared. And in the example above the second query will revert to using the master shard. Was this changed intentionally? Would it be an idea to make this behaviour configurable in octopus, to provide users an easier upgrade path?

Cheers