On 30/11/2010 11:10 PM, Jeremy Evans wrote:
On Nov 30, 12:01 pm, Gary Doades<[email protected]> wrote:
Is is possible for Sequel to raise an error if a non-existent shard is
used in a call to .server or any other method that takes a :server option?
We've had some hard to track down problems because of Sequel falling
back to the :default server if given a server that does not exist. In
our case usually because it was mis spelled or wrong case. I.e someone
should have used :set123, but instead used :Set123. Having Sequel raise
an exception in such cases would make these problems mush easier to find
and also avoid potential database corruption or showing sensitive data
to the wrong user.
I don't mind if it is an option (on DB or call to Sequel.connect
perhaps), but it's hard to code around otherwise.
Makes sense to me:
https://github.com/jeremyevans/sequel/commit/1c4e30c58e77f1af6cc7a9eb75e5a326492d959b
Thanks Jeremy, that'll make a big difference.
Cheers,
Gary.
--
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.
