understanding databases

while postgresql is commonly considered an rdbms, or a "database," it may not be commonly understood what is meant specifically by the word database. a database within postgresql is an object-relational implementation of what is formally called a schema in sql99.

put simply, a database is a stored set of data that is logically interrelated. typically, this data can be accessed in a multiuser environment. this is the case with postgresql, though there are well-defined rights and restrictions enforced with that access.

it may not be commonly understood that postgresql can have several databases concurrently available, each with their own owner, and each with their own unique tables, views, indices, sequences, and functions.

in order to create a table, function, or any other database object, you must connect to a specific database via a postgresql client. once connected, you can create an object, which is then owned by the connected database, and therefore is inaccessible from any other database (though a client may have several connections open to different databases).

by keeping fundamental data objects segregated into their own databases in this fashion, you run a smaller risk of running into a naming collision by choosing a table name already chosen for another purpose (e.g., if two users each wanted to have a table called products for two separate applications). this is because neither database has any knowledge of the other database's components, and will not attempt to make any kind of logical relationship between them. furthermore, as the same rule applies to object-relational data objects, users may even create functions and language definitions within their database that are inaccessible to other users connected to other databases running within postgresql.

by default, postgresql installs only one functional database, which is called template1 to represent the template nature of the database. any database created after template1 is essentially a clone, inheriting any of its database objects, including table structure, functions, languages, etc. it is not uncommon to create a default database for new postgresql users with the same name as their postgresql username, as postgresql will attempt to connect to a database with the same name as the connecting user if a database name is not specified.

understanding tables

tables are quite possibly the most important aspect of sql to understand inside and out, as all of your data will reside within them. in order to be able to correctly plan and design your sql data structures, and any programmatic routines toward accessing and applying that data, a thorough understanding of tables is an absolute pre-requisite.

a table is composed of columns and rows, and their intersections are fields. if you have ever used spreadsheet software before (such as excel), these two terms are visually represented in the same manner, and the fields within a table are equivalent to the cells within a spreadsheet. from a general perspective, columns within a table describe the name and type of data that will be found (and can be entered) by row for that column's fields. rows within a table represent records composed of fields that are described from left to right by their corresponding column's name and type. each field in a row is implicitly correlated with each other field in that row. in this sense, columns can be thought of as descriptors for the discrete, sequential elements of a row, and each row can be thought of as a stored record matching that description.

table 3-1 illustrates a simple table called books, used by our imaginary bookstore, book town. we will frequently refer to this table in later examples. each of its stored records describes a book by a numeric identifier, title, author identifier, and subject identifier. these characteristics, from left to right, are described by its columns (id, title, author_id, and subject_id).

as you can see, this describes a table with four columns, in a fixed, left-to-right order, currently populated by six rows (also known as tuples, or records). it is essential to understand that in a relational database, while a table has a fixed column order, rows themselves are inherently unordered. you will see later, as the sql's query structure is explained in chapter 4, that there are ways within sql to order selected rows. however, the rows in the database itself are not automatically ordered in any consistently predictable way. when order is meaningful for a sql query, you must carefully consider and explicitly order records.

every table must have at least one column, but tables may at times contain no rows, because each vertical column corresponds to a relatively fixed attribute of the data represented in that table (such as the title column in the previous example's books table). without a column, a row's contents would be ambiguous; without a row, a table is merely lacking recorded data. as of postgresql 7.1, there is a maximum of 1600 columns to a table, and an unlimited number of rows (i.e., you are limited only by hardware limitations, such as disk space).

in table 3-1, the column names fairly clearly indicate the significance of each column. the decision of how to name columns is fairly arbitrary, though, and care must be taken in planning table names and conventions to avoid ambiguity.

though it may not be immediately obvious, each of the columns of a table have an associated data type. while a column's data type helps to further describe the sort of information it contains, it constrains the kind of data that may be inserted into the column. for example, the author_id column is of type integer; this signifies that any insertion attempts not consisting of pure a integer (e.g., 110a) will fail. these types are described in more detail in the section called data types."

this section introduced the general concepts of how data is logically arranged in a relational database and within tables. the next section explains why statements are the basis for all interactions with the database.