In his 2004 article Introduction to Databases, Paul Tero provides a simple explanation of what a database is and what it can do for websites. To begin, he clarifies the definition by stating that the term can refer to both the data ("bunch of information") stored or entered into a computer and the software used to store and sort the data. Tero illustrates the fundamentals of a database by comparing it to the physical filing systems used prior to computer databases. A business may have a "client" file in which it keeps information like contact information, and it may also have a "projects" file in which it keeps information like a description of the project, current status, budget, etc. When setting up a database, someone would create tables, like spreadsheets, in which this information would be listed. For example, there might be a "client" table and a "projects" table listing the information with columns designating types of information and rows indicating specific clients or projects. With a database, parts of each table are associated, or related, with each other, allowing data from any of these tables to be sorted with only a few clicks. In Tero's example, client identification numbers from the "client" table are related to client identification numbers in the "projects" table. With this relationship established, information from both tables can be sorted and displayed within a matter of seconds.
Tero continues the article by introducing Structured Query Language (SQL), the differences between static and dynamic Web sites, what a database-driven Web site is, and how to create a database-driven Web site. While these parts of the article go into more depth, and may require a second read for beginners, Tero continues to use simple examples and just presents the essential aspects. He ends with a good conclusion, in which he summarizes the fundamental points readers should, and can, remember. The conclusion is encouraging after a first read: after reading about SQL commands and database-driven Web sites, readers are brought back to the main points of each section, stated in simple, relaxed terms and reminding readers that under all the technical terminology and workings, databases are conceptually simple and ordinary.
Of particular note, Tero's time spent on SQL is not necessary, but is a helpful and wise addition. As Tero states, most database programs hide the SQL behind friendly "menus and toolbars and nice little pop-ups." As a result, users do not need to know SQL to perform a database query. However, understanding how the database performs the sorting process can help users create better queries: by knowing how the program will pull and sort the information, the user can better anticipate what will be retrieved by a query and if this result is what the user wants or needs. Understanding SQL can prevent needless instances of "let's try this combination and see if it returns what we want" (not all instances, since sometimes experimenting is a good thing). Grasping the fundamentals of SQL also builds users' confidence in the database and demystifies databases just enough to build curiosity and familiarity, instead of fear and avoidance.
No comments:
Post a Comment