You should have one class table, with necessary sc...
# flutter
s
You should have one class table, with necessary schema. The approach you are thinking is not practical. Plus how the application will remember which table is for which user