Home
Designing databases
The first step in creating a relational database is to construct a data model, which is a precise, complete definition of the data you want to store. After you prepare your data model, you must implement it as a database and tables. To implement your data model, you first select a data type for each column and then you create a database and tables and populate the tables with data. You can also implement fragmentation strategies and control access to your data.
Designing and Implementing a Database
The Informix® Database Design and Implementation Guide provides information to help you design, implement, and manage your Informix databases. It includes data models that illustrate different approaches to database design and shows you how to use structured query language (SQL) to implement and manage your databases.
Managing databases
Grant and limit access to your database
Views
Restrictions on views

Designing databases
The first step in creating a relational database is to construct a data model, which is a precise, complete definition of the data you want to store. After you prepare your data model, you must implement it as a database and tables. To implement your data model, you first select a data type for each column and then you create a database and tables and populate the tables with data. You can also implement fragmentation strategies and control access to your data.
- Designing and Implementing a Database
  The Informix® Database Design and Implementation Guide provides information to help you design, implement, and manage your Informix databases. It includes data models that illustrate different approaches to database design and shows you how to use structured query language (SQL) to implement and manage your databases.
  - Basics of database design and implementation
  - Managing databases
    - Table fragmentation strategies
    - Grant and limit access to your database
      - Use SQL to restrict access to data
      - Control access to databases
      - Grant privileges
      - Use SPL routines to control access to data
      - Views
        Create views
        Restrictions on views
        When the basis of the view changes
        The tables and views on which you base a view can change in several ways. The view automatically reflects most of the changes.
        Modify with a view
      - Privileges and views
    - Distributed queries
  - Object-relational databases

Restrictions on views

Because a view is not really a table, it cannot be indexed, and it cannot be the object of such statements as ALTER TABLE and RENAME TABLE. You cannot rename the columns of a view with RENAME COLUMN. To change anything about the definition of a view, you must drop the view and re-create it.

Because it must be merged with the user's query, the SELECT statement on which a view is based cannot contain the following clauses or keywords:

INTO TEMP: The user's query might contain INTO TEMP; if the view also contains it, the data would not know where to go.
ORDER BY: The user's query might contain ORDER BY. If the view also contains it, the choice of columns or sort directions can be in conflict.

A SELECT statement on which you base a view can contain the UNION keyword. In such cases, the database server stores the view in an implicit temporary table where the unions are evaluated as necessary. The user's query uses this temporary table as a base table.