New answers tagged normalization
Consider what the second design implies. To me it implies OLTP operations such as update Days set Date = '02.02.2015' where DayID = 1001; This is almost certainly not what you want in an OLTP application. Or in a data warehouse type application it implies that Days is a dimension, and Main is a fact table. However you would normally see a hierarchy in a ...
Normalization for tiny applications in my opinion is overblown and not needed in my humble opinion and experience. I would focus on customer experience, scalability, and ease of management of code. If your code will scale to meet your customers needs, is performant, and you're happy with managing it then it's good enough. Of course things change when you ...
There is not a real need to have a dates table. However, there are some cool things you can do with a dates table such as add columns to that table that have different pieces of information about that day such as holidays or weekends or week of the year, etc. Instead of doing a function to get that information.
For convenience, define the (implied) numbering of your question: A->D BD->E AC->E DE->B Then substituting 1 and 3 into 4 gives (A)(AC) -> B which reduces to just 5. AC -> B.
Top 50 recent answers are included