Is there a benefit to App Relations over unique id strings?
- 0
- Flutter
- Web
- Cloud
- React Native
- Self Hosted
I'm trying to get my first Appwrite site together and I need to either use the Relations or do the manual method using UUID strings. The problem I'm finding is that when I need to reference the relation in my TypeScript code, I have a problem where I have to define the interface first and sometimes there are 2-way references. I'm failing to see the benefit of relations. How is it any different than storing an array of strings? Isn't TypeScript going to give me back an array of either UUID strings or JS Objects. Seems to me like the old method of just storing the count as a column/attribute and an array of strings makes more sense because you can select the count and/or the UUID string array. Do you know of any benefits to the Relations?
Recommended threads
- FCM Message error
When creating a message target via flutter sdk via ``` final target = await _account.createPushTarget( targetId: targetId, identifier: deviceTok...
- Bulk API limitations in self-hosted serv...
Environment: Appwrite Selfhost SDK: node-appwrite 28.0 Calling `upsertRows` (also applies to `createRows`/`updateRows`/`deleteRows`) with more than 100 rows fa...
- Self Hosted GitHub connection not adding...
After upgrading to 1.9.6 i noticed that i cannot search for new repositories when trying to add new functions. I removed the existing github connection via Set...