Result unmarshalling with commands (geospatial queries) about mgo HOT 6 CLOSED

Hi @h-marvin

The original mgo driver doesn't provide any geospatial operation abstractions so talking to MongoDB directly is the only option.

I started to reply to this with an example of how you would go about performing a geoNear query and processing the results, but it wasn't much more work to turn it into an actual driver implementation - check out the feature/geospatial-geoNear branch, specifically the geoNear query example.

This is a proof of concept and not a supported feature yet, but please do try it out and leave some feedback (even a "yes, works for me" or "no, totally broken!") - if it's useful it may be merged into the main driver at some point- the API should be considered unstable and may change until this happens.

Feel free to open PRs against the branch if you have any ideas!

Dom

from mgo.

Hi @domodwyer. I just tested the code and everything works as expected at first glance. Thanks again for you work; much appreciated! I'll keep watching this issue to be notified once the code makes its way onto master 🎉

from mgo.

Also, if wrapping the result would be the way go, any hint for how to properly do that?

type cmdResult struct {
	Results []actualType `bson:"results"`
}

func someFunc() ([]actualType, error) {
	cmd := bson.D{...}
	result := cmdResult{}
	err := db.Run(cmd, &result)
	return result.Results, err
}

This doesn't seem to be doing the trick. The returned slice has the proper length, but the actualType elements do not get properly populated.

from mgo.

Hello @domodwyer. I've been busy the last days and haven't found the time to trying what you proposed. I haven't forgotten about you and want to thank you in advance. I will provide you with feedback once I came around having a look at it and trying it with my code.

from mgo.

Awesome, no rush!

from mgo.

Hi @h-marvin

That's great news, thanks for trying it out! I'm going to cut a release from development in the next week or so, after that I'll open a PR to development and we'll have a team discussion about the best way to move (partial) geospatial support into the driver.

Thanks!
Dom

from mgo.