Perhaps a bit outside of the scope of this discussion, but the reason for data normalization and SQL is because of an outdated paradigm. Data storage used to be really expensive and storing redundant information is therefore cost prohibitive. These days, storage is cheap and we're CPU bound more so than disk space bound.
To cut a long story short some data redundancy isn't a bad thing and in fact if you look at NoSQL engines they actually prefer data redundancy as a means to increased query performance.
The answer here is, it depends how relevant normalization is with respect to its context.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Perhaps a bit outside of the scope of this discussion, but the reason for data normalization and SQL is because of an outdated paradigm. Data storage used to be really expensive and storing redundant information is therefore cost prohibitive. These days, storage is cheap and we're CPU bound more so than disk space bound.
To cut a long story short some data redundancy isn't a bad thing and in fact if you look at NoSQL engines they actually prefer data redundancy as a means to increased query performance.
The answer here is, it depends how relevant normalization is with respect to its context.