Skip to content
This repository was archived by the owner on Aug 12, 2022. It is now read-only.
This repository was archived by the owner on Aug 12, 2022. It is now read-only.

Misleading documentation around indexing for 2d geospatial index #243

Open
@vinayvinay

Description

@vinayvinay

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions