I need some Database structure tips

I have a datatype called Teachers, and a datatype called School.

When a school contacts a teacher i want the school to be able to add things like comments (data type), Booking (data type) and so on that is linked to this teacher. What is the best way to do this?

Is it to create a new thing (TeacherSchool data type):

  • Teacher (Teacher data type)
  • Booking (Booking data type)
  • Comments (Comments data type)

or should i in the Teacher add Comments and Bookking data fileds and in then use repeating group to only display current user comments school is HelloSchool?

Hope you get what im trying to do otherwise i will try to explain better.

Thankful for any help!

Create a new thing and each instance of that thing will represent a relationship between a school and teacher

Hi Alex, thanks for your comment. What am i creating as a new thing?

This :point_up_2:

But i read that connecting databases is most of the time not necessary or a good idea?

Connecting datatypes is fine and necessary in many cases

Okey thanks then i will go this route, when displaying the TeacherSchool should i then filter by Current user School?

Depends on the context. Most likely you’d want to show this datatype in multiple places to different kinds of users. Each instance may require different search constraints

Okey thank you, database structure is for sure the most hard thing for me to get a good grip on. Just so i understand:


  • Teacher
  • School


  • User (user)
  • Firstname
  • Lastname
  • Email
  • Phone
  • Adress
  • Picture
  • etc
  • etc
  • etc


  • Name
  • Adress
  • TeacherSchool
  • User (user)


  • Text
  • User (user)
  • image
  • file


  • Date
  • Title
  • Text


  • Teacher (teacher)
  • Comment (comment)
  • Booking (booking)
  • School (school)

When a School contacts a Teacher:
Create a new thing > TeacherSchool:

  • Teacher = Current cells Teacher
  • School = Current user School

Am i understanding this correctly? So by connecting lets say Teacher & School to TeacherSchool it will not be bloated? Lets say a school contacts 50 teachers or more and each teacher has a lot of data fields?

I can’t advise you on the specifics of each datatype because I’m not familiar with your requirements. Based on what you posted I’d say there’s probably no need to have a teacher datatype. You can create a role option set, create a Techer option, then tie that to the user datatype. Also, School probably shouldn’t have a TeacherSchool field.

Send me a message if you want to set up a consultation that way I can understand your requirements in full and advise on you on a DB structure, privacy rules, and the best way to fetch the data.