Monday, February 29, 2016

Re: Absolute beginner question -- recipes

On 29/02/2016 8:54 PM, Simon Gunacker wrote:
> Well, as far as I know hierarchical relationships are hard to model in
> relational databases;

Definitely incorrect. Hierarchical is merely a subset of relational.
Relational can handle hierarchical 1:n:m very easily plus n:1, n:m as well.

Relational databases are the most widely used today because they can
solve most real world modelling.

On that topic you should try to ignore database design initially and
instead try to understand the real world relationships between your data
types. Only then should you model the solution you need to provide.

I would be surprised if you couldn't solve most real world design
problems with 1:1, 1:n, n:1 and n:m relationships.

The closer your schema is to the real world, the easier it will be to
represent it in a relational (ie Django ORM) database. I believe best
practice is to ignore shortcuts aimed at performance initially and make
your design perfectly represent the real world. Only when it displays
performance problems not fixable with caching should you try and
introduce corner cutting in your design.

</rant>

Mike


--
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+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/56D432D6.9030005%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment