ForĮxample, you could have a users collection to contain your various users, eachįirst : "Alan" last : "Turing" born : 1912Ĭloud Firestore is schemaless, so you have complete freedom over whatįields you put in each document and what data types you store in those fields.ĭocuments within the same collection can all contain different fields or storeĭifferent types of data in those fields. There are some differences (for example, documents support extra data types andĪre limited in size to 1 MB), but in general, you can treat documents asĭocuments live in collections, which are simply containers for documents. You may notice that documents look a lot like JSON. Structure the user's name from the example above with a map, like this: You can also useĪrrays or nested objects, called maps, to structure data within a document.Ĭomplex, nested objects in a document are called maps. Note: Cloud Firestore supports a variety of data types for values:īoolean, number, string, geo point, binary blob, and timestamp. Each document isĪ document representing a user alovelace might look like this:įirst : "Ada" last : "Lovelace" born : 1815 Lightweight record that contains fields, which map to values. In Cloud Firestore, the unit of storage is the document. Or document does not exist, Cloud Firestore creates it. Simply assign data to a document within a collection.
Like strings or complex objects like lists.Ĭollections and documents are created implicitly in Cloud Firestore. Subcollections and nested objects, both of which can include primitive fields Optimized for storing large collections of small documents.Īll documents must be stored in collections.
Instead, you store data in documents, which areĮach document contains a set of key-value pairs.
Cloud Firestore is a NoSQL, document-oriented database.
0 kommentar(er)
