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
Copy file name to clipboardExpand all lines: README.md
+19-9
Original file line number
Diff line number
Diff line change
@@ -307,21 +307,31 @@ Additionaly for elasticsearch6 the number of shards, number of replicas, the ref
307
307
Use the `firestore` type to support Google's Firestore database, and store your KeyFile in a location accessible by your application.
308
308
309
309
```javascript
310
-
constoptions= {
311
-
repository: {
312
-
type:'firestore',
313
-
projectId:'YOUR_PROJECT_ID',
314
-
keyFilename:'/path/to/keyfile.json',
315
-
},
316
-
};
310
+
constoptions= {
311
+
repository: {
312
+
type:'firestore',
313
+
projectId:'YOUR_PROJECT_ID',
314
+
keyFilename:'/path/to/keyfile.json'
315
+
},
316
+
};
317
317
```
318
318
319
319
### Find Queries
320
320
321
-
Find queries in Firestore are not compatible with MongoDb syntax. The query parameter passed to `find` or `findOne` should be an array with the separate query fields as individual elements, as they will be `apply`'d and passed to the `where` function on the `Query` object.
321
+
Simple (equality comparison) find queries are supported by passing javascript objects as the query parameter, or more complex queries can be executed via nested arrays. In the case of multiple key/value pairs or nested arrays, the composite predicates form logical ANDs.
0 commit comments