On 01/12/2010 10:52 PM, Jeremy Evans wrote:
I think it just needs stating that if you override the :servers_hash
option then you MUST add a valid :read_only entry to the servers hash.
That seems to do the trick.
Except that that isn't the case. For example, consider the case where
you override the :servers_hash option with Hash.new(:bev1234).
Like I said, if you'd like some documentation added/changed, please
submit a *patch*. If it's not important enough for you to submit even
a simple documentation patch, it's probably not worth modifying the
documentation in the first place.
Ok, it's a fair point, but that's why I'm trying to find out what is
needed and what isn't.
To be honest, I'm not sure how to generate an actual *patch* for you
under Windows, which is where I'm at right now.
As far as I can see then it boils down to:
If you specify a :servers_hash option to raise an exception for non
configured shards you also need to specify a :read_only entry in your
:servers option for the case where a shard is not specified. In most
cases it is sufficient to add a :read_only entry to use the :default
shard by adding an entry :read_only => {}.
Is this (more) correct according to the current code?
--
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sequel-talk?hl=en.
