Wow I just wrote a big post and SO choked and hung on it, and when I hit my back button to resubmit, the markup editor was empty. aaargh. So here I go again… Regarding Stack Overflow, it turns out that they use SQL server 2005 full text search. Regarding the OS projects recommended by … Read more
UserRelationship ==== RelatingUserID RelatedUserID Type[friend, block, etc] Agree that mutuality doesn’t belong as a column; breaks normalization.
This is a little bit dated question, but for completeness. What about PgModeler? According to their github repo it’s under GPL3. Schema creation works well.
Here is how I ended up solving this problem. I decided to use a dictionary to store data that is unique to each notification type. I then serialize that dictionary object into a binary string and store that in the database along with each notification. I have a template assigned to each notification type that … Read more
A star schema really lies at the intersection of the relational model of data and the dimensional model of data. It’s really a way of starting with a dimensional model, and mapping it into SQL tables that somewhat resemble the SQL tables you get if you start from a relational model. I say somewhat resemble … Read more
Definitely store them in the main table with a column to indicate whether the data is approved or not. When the change is approved, no copying is required. The extra work to filter the unapproved data is the sort of thing databases are supposed to do, when you think about it. If you index the … Read more
Given that the badge criteria can be arbitrarily complex, I don’t think you can store it in a database table broken down into “simple” data elements. Trying to write a “rules engine” that can handle arbitrarily complex criteria is going to take you down the path of basically re-writing all the tools that you have … Read more
I would prefer “Clients_Brokers” (pluralizing both names to indicate many-to-many).
A few points: Learn as much as you can about problem domain. You can’t create good data model without knowing what you’re designing for Have good knowledge about data types provided by your database provider How to properly use normalisation and design tables Performance: when and how to apply indexes, how to write efficient queries … Read more
I think it’s a general rule of thumb to stay away from mystical bitstrings that encode the meaning of the universe. While perhaps clunkier, having a table of possible permissions, a table of users, and a link table between them is the best and clearest way to organize this. It also makes your queries and … Read more