were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale and architecture of the = name; SELECT * FROM myview; Making liberal use of views is a key aspect of good SQL database design. Views allow you to en- capsulate the details of the structure of your tables, which might change is a concept from object-oriented databases. It opens up interesting new possibilities of database design. Let's create two tables: A table cities and a table capitals. Naturally, capitals are also cities

were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale and architecture of the = name; SELECT * FROM myview; Making liberal use of views is a key aspect of good SQL database design. Views allow you to en- capsulate the details of the structure of your tables, which might change is a concept from object-oriented databases. It opens up interesting new possibilities of database design. Let's create two tables: A table cities and a table capitals. Naturally, capitals are also cities

were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale and architecture of the = name; SELECT * FROM myview; Making liberal use of views is a key aspect of good SQL database design. Views allow you to en- capsulate the details of the structure of your tables, which might change is a concept from object-oriented databases. It opens up interesting new possibilities of database design. Let's create two tables: A table cities and a table capitals. Naturally, capitals are also cities

presented in The design of POSTGRES , and the definition of the initial data model appeared in The POSTGRES data model . The design of the rule system at that time was described in The design of the POSTGRES POSTGRES rules system. The rationale and architecture of the storage manager were detailed in The design of the POSTGRES storage system . POSTGRES has undergone several major releases since then. The first = name; SELECT * FROM myview; Making liberal use of views is a key aspect of good SQL database design. Views allow you to en- capsulate the details of the structure of your tables, which might change

presented in The design of POSTGRES , and the definition of the initial data model appeared in The POSTGRES data model . The design of the rule system at that time was described in The design of the POSTGRES POSTGRES rules system. The rationale and architecture of the storage manager were detailed in The design of the POSTGRES storage system . POSTGRES has undergone several major releases since then. The first = name; SELECT * FROM myview; Making liberal use of views is a key aspect of good SQL database design. Views allow you to en- capsulate the details of the structure of your tables, which might change

presented in The design of POSTGRES , and the definition of the initial data model appeared in The POSTGRES data model . The design of the rule system at that time was described in The design of the POSTGRES POSTGRES rules system. The rationale and architecture of the storage manager were detailed in The design of the POSTGRES storage system . POSTGRES has undergone several major releases since then. The first = name; SELECT * FROM myview; Making liberal use of views is a key aspect of good SQL database design. Views allow you to en- capsulate the details of the structure of your tables, which might change

were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale and architecture of the = name; SELECT * FROM myview; Making liberal use of views is a key aspect of good SQL database design. Views allow you to en- capsulate the details of the structure of your tables, which might change is a concept from object-oriented databases. It opens up interesting new possibilities of database design. Let's create two tables: A table cities and a table capitals. Naturally, capitals are also cities

were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale and architecture of the = name; SELECT * FROM myview; Making liberal use of views is a key aspect of good SQL database design. Views allow you to en- capsulate the details of the structure of your tables, which might change is a concept from object-oriented databases. It opens up interesting new possibilities of database design. Let's create two tables: A table cities and a table capitals. Naturally, capitals are also cities

were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale and architecture of the = name; SELECT * FROM myview; Making liberal use of views is a key aspect of good SQL database design. Views allow you to en- capsulate the details of the structure of your tables, which might change is a concept from object-oriented databases. It opens up interesting new possibilities of database design. Let's create two tables: A table cities and a table capitals. Naturally, capitals are also cities

were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale and architecture of the = name; SELECT * FROM myview; Making liberal use of views is a key aspect of good SQL database design. Views allow you to en- capsulate the details of the structure of your tables, which might change is a concept from object-oriented databases. It opens up interesting new possibilities of database design. Let's create two tables: A table cities and a table capitals. Naturally, capitals are also cities