You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 12, 2022. It is now read-only.
This line mandates that the field used for 2d geospatial indexing must be an Array. mongodb doesn't mandate anything like that, instead it is open to an Array or embedded document, but only mandates the correct order [lon, lat].
i ran benchmarks against indexes created as both Array and embedded document, doesn't make any difference. then why is mongoid mandating the usage of Array ?
please make it such that it mirrors mongodb requirements, or if there is a good reason for mongoid to mandate it, then make it clear here.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This line mandates that the field used for 2d geospatial indexing must be an
Array
. mongodb doesn't mandate anything like that, instead it is open to anArray
or embedded document, but only mandates the correct order [lon, lat].i ran benchmarks against indexes created as both
Array
and embedded document, doesn't make any difference. then why is mongoid mandating the usage ofArray
?please make it such that it mirrors mongodb requirements, or if there is a good reason for mongoid to mandate it, then make it clear here.
The text was updated successfully, but these errors were encountered: