Re:MongoDB 1.8 (stable) released
by thibaut_barrere on Thursday March 17, 2011 @12:04PM
(#2336596)
I don't know really - if limitations are documented like they are apparently, it's really not an issue for me - I don't feel cheated (but it's really an opinion!).
Your mileage may vary as they say: I used the GIS since 1.6 and it was very helpful for me in this form already :)
The limitations are documented as foot/side notes.
Analogy: It's like seeing "ACID compliance!" on a feature list, then finding buried in the documentation that is only the case for single-document transactions in unordered collections on a single machine only.
The new feature might be useful to some but including it on a feature list without disclaimer is misleading.
Re:MongoDB 1.8 (stable) released
by thibaut_barrere on Thursday March 17, 2011 @01:46PM
(#2337114)
I understand your analogy really :)
Really curious: are you using mongo currently? Or browsing the docs?
For example: If they were truly using a "spherical model", then one would not expect to have queries fail at the poles & dateline, would you?
At least it is documented and fails hard with an error rather than giving wrong results, so a developer can quickly figure out the weak spots --- though I bet a lot of people would prefer the wrong results to queries that cause exceptions in their systems.
> Do you mean you think they don't know how to do it?
I think it has more to do with the absurdly low bar they've set for themselves to check the "geospatial" box than it does with competence.