Settings and activity
10 results found
-
1 vote
Cedvdb shared this idea ·
-
190 votes
Scheduled Backups for Firestore is now in public preview:
-
1 vote
-
24 votes
An error occurred while saving the comment -
50 votes
-
629 votes
-
109 votes
-
87 votes
An error occurred while saving the comment @frank
The documented solution has the following issues:
- request more documents than necessary
- does not allow much flexibility on modelization
- requires multiple parts of the application to be aware that a collection has a geo field.I'd propose something like:
```collection.within(
radius: 1000,
center: position,
latitudeField: 'position.latitude',
longitudeField: 'position.longitude'
)
```This would allow people to not rely on a GeoPoint data type furnished by firebase and be able to rely solely on Json, which is possible currently for other data types and which brings a lot of advantages:
- no need for an additional layer to abstract firebase specifics
- is easier on code generation tools.----
Just to be clear, I advice to not have a special data type on the firestore side for geo queries, keep it json like and deprecate the current geo data type. Have a geo-hash-index opt-in index on the back-end side.
-
205 votes
A small update on this: we have been scoping all the work, and are prioritizing tasks now. We will share progress updates at the beginning of Q2 2024.
-
444 votes
Imo a better alternative would be to wrap the c++ sdk (and therefor making the c++ sdk solid) and have each platform use that.