ホワイトペーパー

The dictionary definition of a heuristic is “Computers, Mathematics: pertaining to a trial-and-error method of problem solving used when an algorithmic approach is impractical.” which means this is what you do when you do not know what to do next. The term “normalization” comes from Dr. Codd, who borrowed it from the thencurrent political climate in which we were trying to normalize relations with the Soviet block. The goal is to remove redundancy from a database schema and to have the schema maintain some data integrity without procedural code.

Most of us began programming in procedural languages. But SQL is a declarative language. Chris Date described the difference as “What, not How” in one of his books. SQL has three sub-languages; the DDL or Data Declaration Language, the DML or Data Manipulation Language and the DCL or Data Control Language.

The 2000 book Me Talk Pretty One Day (ISBN 978-0316777728) is a collection of essays by American humorist David Sedaris. He moved to a rural part of Normandy, France, and had no idea how to speak or read French at the time. The humor comes from his frustrated attempts to learn the language and culture. The locals knew him as the American idiot who scares their animals by screaming. The warning on electrified fences was in French and a great source of amusement for the neighbors

Dr. Codd’s original relational algebra had eight basic operations. Since RDBMS is based on set theory the first four are traditional set operations: intersection, set difference, union and product These operations are available in SQL, respectively, as INTERSECT, EXCEPT, UNION, and CROSS JOIN respectively.

SQL is the first programming language to have temporal data types in it. If COBOL had done this, we would never have had the "Y2K Crisis" we survived a few years ago. SQL- 92 added temporal data to the language, acknowledging most of what was already in most SQL product by that time. The problem is that each vendor made a trade-off internally. We will get into SQL code later, but since this is an area where people do not have a good understanding, it is better to start with foundations.

If you cruise SQL programming newsgroups, you will eventually find a post for what is called EAV (“Entity-Attribute-Value”) tables. It is a very common schema design error for programmers who started with an OO, work with NoSQL (attribute, value) pairs or a loosely typed programming language.

Cardinality has nothing to do with song birds or Catholic church officials. It is a term from set theory that deals with the size of a set. Originally, Georg Cantor invented the term, so that he could talk about infinite sets like integers, real numbers, irrationals, power sets and so forth.

Pick any two positive integers. Add them and get a third number. Then use the last two numbers and do it again. And again, for a long time. Finally, take the ratio of the last two numbers. Without any other information I am sure that ratio will be ~1.618033988749894848204586834. This is called the Golden Ratio or φ, and it works out to (1 + √5)/2. It occurs as a law of nature. Nobody programmed it, per-arranged it or used a magic trick on you.