Hi there, I've been working in no-code for a few months and hitting lots of limitations. The latest tool that was recommended to me is Appgyver. It seems great, but it doesn't include a database. They recommend using RestDB and it looks good enough to me. I used the database in Bubble and so I have some exposure to DB conventions.
My questions are regarding the "user" collection that is the default;
Do I use this for every single person that will use the app, regardless of their role? For example, a marketplace has users on the demand side, and different users on the supply side, (or the user could be on both sides like Craigslist), do I use the "user" collection for all? Or would I create different collections for different types of users?
Then, if I would use different collections for different types of roles, should I also have a separate collection for a "user", and then a "customer" if that user becomes a subscriber?
It seems it would get really messy trying to shoehorn all types of users into the same collection with too many fields and convoluted access rules.
Any insight would be appreciated, thanks! (There was no database group to post this too.)
Typically you would have one "collection" for users. And then without getting too deep into the weeds, let's say you'd then have a field for defining the "role" of that user (ex: seller, buyer, both). Then you could base everything off of the "role" field. So to answer your questions:
Hope that helps!
This is interesting, thanks for the detailed response!
I can definitely see how putting everyone in the same bucket makes it easier reference and avoid duplicate entries across collections. It just seems easier though to screwup the privacy settings for different roles, but I guess I'll know more as I get into it. :-)
Yeah, especially when you get into stuff like managing passwords, trust me, you'll want them all in the same place using the same system!
If you need help with anything feel free to dm me. I like database stuff.
Will do, talk soon.