custom fields user table
hi, what you guys recommend me for this?
i have a php system without any framework
i want to migrate to filament
currently it have two tables one for admin login, one for client login
should i have the same in filament? i mean two diff table for login? the difference is the client table have many custom fields like address, identification, passport, phone, mail, services, mobile and so on that admin table doesn't have. or should i use one table only of users and have a client_detail table for example with a foreign key that links to the user table?
thank you
i have a php system without any framework
i want to migrate to filament
currently it have two tables one for admin login, one for client login
should i have the same in filament? i mean two diff table for login? the difference is the client table have many custom fields like address, identification, passport, phone, mail, services, mobile and so on that admin table doesn't have. or should i use one table only of users and have a client_detail table for example with a foreign key that links to the user table?
thank you
Solution
both approaches are possible. However, I would keep a single table and using a HasOne relationship to store the client-specific fields.
Laravel is a PHP web application framework with expressive, elegant syntax. We’ve already laid the foundation — freeing you to create without sweating the small things.
