🚀 Seeking Expert Advice for working with list of data 🚀
Project Overview: I'm developing a POS app for pharmacy shop to enhance the efficiency of pharmacists and improve customer experiences. The app includes features like sales and order management, inventory tracking and so on...
Current Challenge: I'm specifically looking for guidance on managing relationships between different data collections in Appwrite. My data model includes complex attributes, and I'm wondering how best to establish connections between items, suppliers, payments, and other related entities. I checked on appwrite official docs but there is nothing about working with list of data.If I put a attributes as a array how can I add relation to others collection's document. Example. I have a db collection named "Order". It has a array attriute named " items ". " items " will be included list of order Items. I have no idea about that. Should I put all order item data as List of Map to "items" attribute. Or make a new collection for order items and how to add relationship at Order collection's attribute "items" .
How You Can Help:
Database Relationship Tips: If you've worked with complex data models and relationships in Appwrite, your insights would be invaluable. How do you establish connections between different collections, especially when dealing with arrays of data and relationship to arrays? Flutter Expertise: If you have experience with Flutter, especially in building POS applications, I'd love to hear your best practices and any hurdles you might have overcome. Appwrite Wisdom: Any tips, tricks, or best practices related to Appwrite, real-time data synchronization, or handling complex data structures would be greatly appreciated.
Feel free to reply here with your insights or DM me directly if you prefer a one-on-one discussion. Thank you in advance for your time and expertise. 🙌
Happy coding, Ya Wai Aung yawaiaung_166
🚀 Seeking Expert Advice for working with list of data 🚀
A couple other comments:
- Don't use arrays for things you need to query because query operations are not supported.
- Don't use arrays for things you will be updating concurrently because you need to do a full update and multiple full updates can conflict.
- Relationship support is experimental. If you don't use relationships, you can still manually do the relationships using a string attribute for the ID of the related document.
