On 20/05/2018 1:45 PM, Daniel Germano Travieso wrote:
There is no really definitive approach to handle this, and you could
do it either way.
Either option works, but for a philosofical point of view, if there is
no significant difference between the user types, the first approach I
tend to beli
There is no really definitive approach to handle this, and you could do it
either way.
Either option works, but for a philosofical point of view, if there is no
significant difference between the user types, the first approach I tend to
believe is the most logical one.
However, as a optimal ap
I inherited a system which has one User model, and a Profile model that is
1-to-1 with User. The type-of-user information is carried in a required
"role" property in the Profile. I think that is a well-established
approach.
I am curious to hear what people think of the tradeoffs between (Use
I would make a UserType table and have a foreign key from your user model
to it, or maybe just have an enumerated type in your user model depending
on how much custom logic there is to each user type.
On Tue, May 15, 2018 at 11:50 AM Frankline wrote:
> Hello Everyone,
>
> I am developing an API
4 matches
Mail list logo
