I need advice regarding the following use case:
I’m building a booking system for a swimming pool complex at a school. An adult swimmer can book for him/herself, but a coach or teacher must be able to book for kids. School management does not allow kids to book for themselves.
This is my question, should I create an additional user table for kids that does not have email addresses, or is it better to create a fictional email address for every kid and make use of the built in Bubble user table?
I’ll greatly appreciate suggestions in this regard.
It depend on, if kids should login as user and do tthings then you definitely need emails, as user a unique entity in bubble which need emails.
But of kids do not need to login and do task then you can create a separate entities like kids and link them with a teacher or parents
Thank you so much. You confirmed my suspicion.
I’d create a data type that is ‘profile’ and have a field that distinguishes between kid, adult or teacher/coach. Setup conditions so that kids can not book themselves. This way, you have only one data type you need to work with to know ‘who are all the swimmers in the pool at this hour’…do not overcomplicate things by having different data types for kids versus adults versus coach, just using a single field on a ‘profile’ data type that distinguishes them.
Thank you, this is exactly what I am going to do.
1 Like
