| Re: Mr. Stuckle and Mr. Miller - explain normalisation with an example [message #185308 is a reply to message #185275] |
Mon, 17 March 2014 13:56  |
Gabriel
Messages: 11
Registered: March 2014
Karma:
|
Junior Member |
|
|
On 2014-03-16 20:22:39 +0000, richard said:
> I'll bet you won't.
>
> The table I have now consists of the following columns.
> songid,hits, title, author, license.
> Please explain how this data should be normalised.
> And why.
> Thank you.
richard,
Whilst I know that your title quite clearly only wants to ellicit
responses from Mr. Suckle and Mr. Miller quite a few others have been
chipping in. I'd like to offer my pennies-worth too and I know that you
would not want me to feel left out.
Don't worry about data normalisation. You only need to normalise data
as much as is required to achieve the results you want, considering the
possible future that your site may have. It would be sensible to store
author info in a seperate table and link to it using IDs which being an
integer would provide very fast joins.
Don't forget that modern NoSQL databases that are quickly gaining
momentum in the web development world (for good reason - they are very
fast) such as MongoDB don't really even understand data normalisation
as a concept. You just shove the whole lot in, author and all, and
pull the whole lot out and sod repeating yourself.
IMO I do think that from what I have read of your particular site it is
a good fit for the more traditional relational-database approach.
Kind regards
Gabriel
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]