Sunday, July 17, 2016

This Week

1. What's wrong with this picture? 
RB: "From the tabular point of view, does it make sense why we can't have duplicate rows in a relation?"

John Sullivan: "As with everything else in life, it depends what you are trying to do (and exactly what you mean when you talk about a DBMS table v. a formal relation). From an operational (transactional) database point of view, for obvious reasons, you don't want duplicate rows (enforce a natural key). But if you're analysing data from various legacy sources (e.g. spreadsheets) it might be useful. Then again, you might introduce a surrogate key to give you more control over what's going on - again, depends on what you are trying to do." --Question about the relational model

2. Quote of the Week

"The logical model already imposes something of the physical world, depending on which logic you use to define it. Logical modeling and physical modeling... I used to skip the logical model and implement the physical straight into the database. Nowadays, after being infected... ahem, influenced by Martijn Evers, I use PowerDesigner for both." --Ronald Kunenborg

3. To Laugh or Cry?

The NoSQL SQL Illusion (particularly the comments; see also Moving in Circles SQL for NoSQL).

4. Of Interest

And now for something completely different

The PostWest (Oh, No, Not in Nice!)
Pinch me of the week
"Look for empire builders, self-servers in the hiring process — and don’t hire them. All companies screen candidates for skill sets and experience. Everyone wants to hire the best and smartest people they can find." --How Facebook [i.e., Zuckerberg] Tries to Prevent Office Politics [i.e., avoid competitors].
Book of the week (purchase via this link to support this site)

No comments:

Post a Comment