nullable field about mongoose-geojson-schema HOT 6 OPEN

I believe the preferred approach would be deleting the property from the containing object rather than setting it as null. If it's null it'll think there's an object to be cast/validated.

from mongoose-geojson-schema.

I believe the preferred approach would be deleting the property from the containing object rather than setting it as null.

Well that works, but an $unset field doesn't mean the same as a null field.
null is for deliberate absence of value, not set rather means not-really-wanted absence of value.

EDIT: plus

If it's null it'll think there's an object to be cast/validated.

Yeah, that's it, I think one would want to cast null as a geojson polygon (json-type null is ok, plus it works with Object)

from mongoose-geojson-schema.

If you cast null as an empty GeoJSON object then it's going to want coordinate values, and if those are empty any geospatial index you have on Mongo will fail AFAIK. If the property doesn't exist it will simply be absented from the index.

from mongoose-geojson-schema.

any geospatial index you have on Mongo will fail AFAIK

Actually they are sparse by default, and null is ok with sparse indexes.

from mongoose-geojson-schema.

Ok I'll need to check and write a test for this. Thanks for bringing it to my attention. Obviously my knowledge of the Mongo API is a bit rusty!

from mongoose-geojson-schema.

@cyrilchapon I know this is late, but could you give me an example of the schema and data that you were working with? It would be nice to get this working properly with systems requiring sparse indexes.

from mongoose-geojson-schema.