Re: database design approach

[vamsikrishna Aliveli]

Hi ,
If you are using single model you use single model with multiple fields .If
you are using multiple models  you can use Foreign field to refer other
model in current model.(Player model)

On Wed, 1 Feb 2023, 20:33 datasci via Django users, <
django-users@googlegroups.com> wrote:

> I am designing a database for a django project. I already read this
> tutorial that I found really useful:
> https://learndjango.com/tutorials/database-design-tutorial-beginners
>
> I have a question regarding the normalization. The normalization is
> important due that we need to reduce redundant data. But we need to find a
> balance because increasing the complexity is decreasing the performance.
>
> I have a model (Player) that refers to the User Model.  I need to add
> several fields in the Player model. Is it better to put every field in the
> Player model or I can use three levels of complexity?
>
> Approach 1: User Model > Player Model (with many fields)
> Approach 2: User Model > Player Model > Several Different Models for each
> different features.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/NNBgIx_--3-9%40tuta.io
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAPKT8_u402TSaJ9nw8s_6aqf%2B5rKE3%2B5fxwbTfuVDCaphow_sA%40mail.gmail.com.

database design approach

[datasci via Django users]

I am designing a database for a django project. I already read this tutorial 
that I found really useful: 
https://learndjango.com/tutorials/database-design-tutorial-beginners

I have a question regarding the normalization. The normalization is important 
due that we need to reduce redundant data. But we need to find a balance 
because increasing the complexity is decreasing the performance.

I have a model (Player) that refers to the User Model.  I need to add several 
fields in the Player model. Is it better to put every field in the Player model 
or I can use three levels of complexity?

Approach 1: User Model > Player Model (with many fields)
Approach 2: User Model > Player Model > Several Different Models for each 
different features.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/NNBgIx_--3-9%40tuta.io.