Documentation
 
 
 
PrevFast BackwardFast ForwardNext

Chapter 4. Data Definition

Table of Contents
4.1. Table Basics
4.2. System Columns
4.3. Default Values
4.4. Constraints
4.4.1. Check Constraints
4.4.2. Not-Null Constraints
4.4.3. Unique Constraints
4.4.4. Primary Keys
4.4.5. Foreign Keys
4.5. Modifying Tables
4.5.1. Adding a Column
4.5.2. Removing a Column
4.5.3. Adding a Constraint
4.5.4. Removing a Constraint
4.5.5. Changing the Default
4.5.6. Renaming a Column
4.5.7. Renaming a Table
4.6. Privileges
4.7. Schemas
4.7.1. Creating a Schema
4.7.2. The Public Schema
4.7.3. The Schema Search Path
4.7.4. Schemas and Privileges
4.7.5. Usage Patterns
4.7.6. Portability
4.8. Synonyms
4.8.1. Creating a Public Synonym
4.8.2. Deleting a Public Synonym
4.8.3. Public Synonym Namespace
4.8.4. Public Synonym Name Resolution and the Search Path
4.8.5. Public Synonyms and Privileges
4.9. Inheritance
4.10. Partitioning
4.10.1. Overview
4.10.2. Implementing Partitioning
4.10.3. Partitioning and Constraint Exclusion
4.11. Other Database Objects
4.12. Dependency Tracking

This chapter covers how one creates the database structures that will hold one's data. In a relational database, the raw data is stored in tables, so the majority of this chapter is devoted to explaining how tables are created and modified and what features are available to control what data is stored in the tables. Subsequently, we discuss how tables can be organized into schemas, and how privileges can be assigned to tables. Finally, we will briefly look at other features that affect the data storage, such as views, functions, and triggers.

4.1. Table Basics

A table in a relational database is much like a table on paper: It consists of rows and columns. The number and order of the columns is fixed, and each column has a name. The number of rows is variable -- it reflects how much data is stored at a given moment. SQL does not make any guarantees about the order of the rows in a table. When a table is read, the rows will appear in random order, unless sorting is explicitly requested. This is covered in Chapter 6. Furthermore, SQL does not assign unique identifiers to rows, so it is possible to have several completely identical rows in a table. This is a consequence of the mathematical model that underlies SQL but is usually not desirable. Later in this chapter we will see how to deal with this issue.

Each column has a data type. The data type constrains the set of possible values that can be assigned to a column and assigns semantics to the data stored in the column so that it can be used for computations. For instance, a column declared to be of a numerical type will not accept arbitrary text strings, and the data stored in such a column can be used for mathematical computations. By contrast, a column declared to be of a character string type will accept almost any kind of data but it does not lend itself to mathematical calculations, although other operations such as string concatenation are available.

EnterpriseDB includes a sizable set of built-in data types that fit many applications. Users can also define their own data types. Most built-in data types have obvious names and semantics, so we defer a detailed explanation to Chapter 7. Some of the frequently used data types are DATE for dates and time-of-day values, and TIMESTAMP for values containing both date and time.

To create a table, you use the aptly named CREATE TABLE command. In this command you specify at least a name for the new table, the names of the columns and the data type of each column. For example: 


CREATE TABLE my_first_table (
     first_column    VARCHAR2(15),
     second_column   NUMBER
);

This creates a table named my_first_table with two columns. The first column is named first_column and has a data type of VARCHAR2; the second column has the name second_column and the type NUMBER; The table and column names follow the identifier syntax explained in Section 3.1.1. The type names are usually also identifiers, but there are some exceptions. Note that the column list is comma-separated and surrounded by parentheses.

Of course, the previous example was heavily contrived. Normally, you would give names to your tables and columns that convey what kind of data they store. So let's look at a more realistic example: 

CREATE TABLE emp (
    empno           NUMBER(4) NOT NULL,
    ename           VARCHAR(10),
    job             VARCHAR(9),
    mgr             NUMBER(4),
    hiredate        DATE,
    sal             NUMBER(7,2),
    comm            NUMBER(7,2),
    deptno          NUMBER(2)
);

(The NUMBER type can store fractional components, as would be typical of monetary amounts.)

Tip: When you create many interrelated tables it is wise to choose a consistent naming pattern for the tables and columns. For instance, there is a choice of using singular or plural nouns for table names, both of which are favored by some theorist or other.

There is a limit on how many columns a table can contain. Depending on the column types, it is between 250 and 1600. However, defining a table with anywhere near this many columns is highly unusual and often a questionable design.

If you no longer need a table, you can remove it using the DROP TABLE command. For example: 

DROP TABLE my_first_table;
DROP TABLE emp;

Attempting to drop a table that does not exist is an error. Nevertheless, it is common in SQL script files to unconditionally try to drop each table before creating it, ignoring the error messages.

If you need to modify a table that already exists look into Section 4.5 later in this chapter.

With the tools discussed so far you can create fully functional tables. The remainder of this chapter is concerned with adding features to the table definition to ensure data integrity, security, or convenience. If you are eager to fill your tables with data now you can skip ahead to Chapter 5 and read the rest of this chapter later.

PrevHomeNext
Value ExpressionsUpSystem Columns
 
 ©2004-2007 EnterpriseDB All Rights Reserved