Skip to content
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.

Poorly Formed Query with \n Causes a Connection Error #368

Open
gutter007 opened this issue Apr 24, 2015 · 0 comments
Open

Poorly Formed Query with \n Causes a Connection Error #368

gutter007 opened this issue Apr 24, 2015 · 0 comments

Comments

@gutter007
Copy link

If you perform:
TestModel.where(:id => "553a64644d6572392b090000\n")

you get:
Uncaught exception: Could not connect to a secondary node for replica set #<Moped::Cluster:70212540271240 @seeds=[<Moped::Node resolved_address="10.10.10.34:27017">, <Moped::Node resolved_address="10.10.10.38:27017">, <Moped::Node resolved_address="10.10.10.39:27017">]>

While I agree this is a horrible query, it should get an error, it shouldn't kill the connection error. If you take the \n out you get the doc out of the database.

thanks.
myles

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant