School Database System

Question

Currently, my team started working on a school Database System as requested by a client. Everything is working so great but I doubt the professionalism in some of our implementation.

- The tech used is python with django, webassembly and solidJS for web.

- Kotlin with jetpack compose for Android/iOS.

- kotlin with jetpack compose, C++ wt designer for gui

The backend is 100% Django api rest framework, postgresql

When we design a model for users, they either a teaching staff or student and we created another model for session and available courses. The doubt here is this

1. Is it more professional to make session, registered course a foreignKey with a user profile?

2. Or make them a ManyToMany relationship with the profile.

Both works fine, but I think one should be more preferable. I'm afraid we'll be having database migration conflict in the future

Answer 1

ManyToMany is most likely the way you want to pursue.

Answer 2

BroFar we actually made a poll, and I'm the only one who support foreignkey. Lol weird

Answer 3

If you want more control over certain data you can always revisit and use foreignkey for selected as an intermediate approach so it isn't unreasonable to consider RuntimeTerror