Logos are powerful. What better way to remind people of a product than an eye-catching, memorable symbol? With that in mind, today we’ll answer the question ‘Why did PostgreSQL choose an elephant for its logo?’ Every product or company has its logo – something that identifies and encapsulates the essence of their brand. In time, it practically becomes the brand: can you imagine McDonald’s without its golden arches? What if the Coca-Cola logo was suddenly done in purple block print?
The Turing Award is an annual prize given by the Association for Computing Machinery (ACM) “for contributions of a technical nature made to the computing community.” It is sometimes referred to as the “Nobel Prize” in Computing. Currently, the prize is 1 million dollars with funding provided by Google. The 2014 Turing Award – announced just three weeks ago on March 25, 2015 – was given to Michael Stonebraker, who earned the award for “fundamental contributions to database systems, which are one of the critical applications of computers today.
MySQL is the world’s most popular and widely used open-source relational database. It was originally founded and developed in Sweden by two Swedes and a Finn: David Axmark, Allan Larsson and Michael "Monty" Widenius, who had worked together since the 1980’s. Why “My”? The name MySQL owes its name to Monty’s daughter My. Indeed Michael, often called Monty, has a habit of naming his projects after his children: MariaDB was named after his youngest daughter and MaxDB was named after his son Max.
Computer databases first emerged in the late 1960s after computers had become powerful enough to handle large amounts of financial, human resources and bank data. Let’s take a look at the history of how modern databases came about. 1960s: navigational databases, mostly hierarchical databases and network databases, were first used 1970: E.F. Codd from IBM introduces the concept of relational databases and the first normal form 1971: second and third normal form are introduced by Codd
Many people wonder why relational databases are called “relational.” Some think that it’s because of a logical entity-relationship model you often start your design with. Or, because you have tables and relationships (aka foreign keys) between them. But that’s not the case. The name comes from the mathematical notion of “relation.” It all started with E. F. Codd who in 1970 (in the article A Relational Model of Data for Large Shared Data Banks) proposed something now called relational algebra as the mathematical foundation of databases.