У нас вы можете посмотреть бесплатно Firestore Tutorial Part 18 - SUBCOLLECTIONS AND CONSIDERATIONS - Android Studio Tutorial или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
In part 18 of the Firestore tutorial, we will learn how to add sub-collections to a Firestore document and how to query these sub-collections. For this we simply add another .collection call on a DocumentReference, which creates a CollectionReference to it's sub-collection. We give this sub-collection a name (collectionPath) and can continue this chain up to 100 levels deep. Like on a top-level collection, we can then add documents to this collection or retrieve the existing documents. Subcollections can also be added directly over the Firebase Console. We will also talk about considerations you have to make when you plan the structure of your database, and when it's better to use nested objects or arrays rather than subcollections. Every Firestore query runs against a single collection, so we can't query across subcollections. We can also not retrieve a document by a value in any of it's subcollection's documents and when we delete a document, it's subcollections don't automatically get deleted as well, which can lead to orphaned collections that still take up space in the database. Since Firestore bills per number of read, write and delete operations on a document, it can make sense to put related data into an array or nested object. Documents on the other hand have 1mb size and 20k field limits and only support approx. 1 write per second. Documents can also not be retrieved partially, which can lead to security issues and use up a lot of network data if they are very big. But since Firestore queries are shallow, we can retrieve a document without automatically downloading it's subcollections or any of the documents in them, and we can easily paginate documents from a subcollection and set up different security rules for them. Those are factors you have to keep in mind when we build your app. Watch the whole playlist: • Плейлист Code for this part: https://gist.github.com/codinginflow/... Firebase explainer video about collections, subcollections and nested data: • Maps, Arrays and Subcollections, Oh My! | ... ____________________ 💻 Find the BEST programming tutorials on TutHub: https://tuthub.io ⭐ Get my MVVM Caching Course now: https://codinginflow.com/caching ❗ Subscribe to the channel: / codinginflo. . 📨 Subscribe to the Coding in Flow newsletter: https://codinginflow.com/newsletter ❓ Join our free developer community: / discord 📣 Follow Coding in Flow on other sites: Facebook: / codinginflow Instagram: / codinginflow TikTok: / codinginflow Twitter: / codinginflow Github: https://github.com/codinginflow 💰 Business requests, sponsoring, etc.: info@codinginflow.com