Search Results

I would think the thing to do is to store the property or properties that are used to calculate the rank and then build an index over them. Rather than trying to force the database to physically stor …

I'm frankly always nervous about throwing away details. For that reason I'd try to find a way to keep handy (or at least archive) the most granular data. That way, if your summarization requirements …

Your basic model is fine. It gives you a standard, normalized intersection (many to many) of events of specific types associated with particular users. Without knowing more about your intentions or …

What you are proposing is a good solution for your requirement of M:N products to categories and hierarchical categories. To avoid exposing yourself to numerous updates: You need to do two things to …

Your "Idea 1" is the best approach as it most naturally and accurately enforces the cardinality between SITE and CLAN/GAME/TEAM. Your other rule that SITE must be only one of CLAN, GAME or TEAM wou …

Important Caveat: You need to look at the link OP provided! It uses the words type and sub-type as jargon in a way which is similar to, but different than what programmers or even data modellers wou …

Do you have a reason to store the searches as individual events or are you only interested in recording which terms were used how many times on any given day? If you just need to record how many time …

What you are proposing is an entity subtyping approach. This would be one common solution to your design problem. Another would be Entity-Attribute-Value (EAV). Type "subtype" or "EAV" into the sea …

The first thing you want to do to keep your thinking straight is to choose some clear terminology. You are using the word "assessment" in two different contexts: (i) a Test and (ii) the results for a …

Most people consider one lookup table to rule them all an anti-pattern. You can see lots of reasons why, and many of them are well described in One lookup table or many lookup tables? which you've al …

If your hierarchy is rigid (i.e. the levels are consistent and mandatory) then there is nothing wrong with representing each level as it's own table. This is your first option, except that instead of …

Self referencing tables can be used to store hierarchical data. For example, see my answer to this question. You can also use self referencing tables to record non-hierarchical relationships which a …

Consider handling all money related transactions using a double entry accounting model. Any real world application will eventually need to handle the complexity that this model supports and it is a w …

SQL employs a concept known as domain name integrity which means that the names of objects have a scope given by their container. Column names have to be unique, but only within the context of the ta …

Computers don't get tired. Nobody has so many employees that the summation over a well-indexed set of rows of vacation actually taken would grind their servers to a halt. What is a problem is precal …