-
Notifications
You must be signed in to change notification settings - Fork 72
Issues between serde and mongo #152
Comments
From trying it out, it seems that updating |
I do not know if its fixed now but I did switch back to rustc_serialize. It was an annoying move though but hopefully serde will become more stable. |
I just tried it out again now that serde @kyeah, I don't suppose you'd have a chance to take a look at updating bson to use serde 0.8? I'm not as familiar with that code as you are, although I can take a stab at doing the update myself if you're busy with other things. |
I can take care of bson today. |
Awesome! Thanks a bunch |
bson v0.3 is out with the fix, should be able to update. sorry for the wait, y'all! |
Assuming the Travis build passes, I'll merge #160 and push out a new version to crates.io |
Just pushed 0.1.6. @dariusc93, if you use the latest version along with bson 0.3, and serde 0.8, it should work fine now. |
Have anyone had issues between serde and mongo? Since recently I ran a
cargo update
there had been an issue where is serde, serde_json, and serde_macro exist along side mongo-rust-driver-prototype would give an error related to quasi but with it commented out in Cargo.toml it does not error out at all. I cannot pinpoint the issue but it seems to be related to serde-deprecated/quasi#54 .Example of Cargo.toml (replace the section for mongodb with either from crates or use git}
I do not know what the reason on why it happens when using mongodb (even tried it with bson-rs and it doesnt error out). At this point i might have to switch back to rustc_serialize :/ .
The text was updated successfully, but these errors were encountered: