mirror of
https://github.com/postgres/postgres.git
synced 2025-08-30 06:01:21 +03:00
Make sure that only one intro is included in the integrated doc.
Multiple intros cause trouble since they have some section elements (e.g. "y2k.sgml") in common leading to duplicate labels. Include emacs formatting hints in the intro*.sgml sources.
This commit is contained in:
@@ -1,84 +1,96 @@
|
||||
<Chapter Id="intro">
|
||||
<TITLE>Introduction</TITLE>
|
||||
<chapter id="intro">
|
||||
<title>Introduction</title>
|
||||
|
||||
<Para>
|
||||
This document is the user manual for the
|
||||
<Ulink url="http://postgresql.org/"><ProductName>PostgreSQL</ProductName></Ulink>
|
||||
database management system, originally developed at the University
|
||||
of California at Berkeley.
|
||||
<para>
|
||||
This document is the user manual for the
|
||||
<ulink url="http://postgresql.org/"><productname>PostgreSQL</productname></ulink>
|
||||
database management system, originally developed at the University
|
||||
of California at Berkeley.
|
||||
|
||||
<ProductName>PostgreSQL</ProductName> is based on
|
||||
<Ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html">
|
||||
<ProductName>Postgres release 4.2</ProductName></Ulink>.
|
||||
The <ProductName>Postgres</ProductName> project,
|
||||
led by Professor Michael Stonebraker, was sponsored by the
|
||||
Defense Advanced Research Projects Agency (<Acronym>DARPA</Acronym>), the
|
||||
Army Research Office (<Acronym>ARO</Acronym>), the National Science
|
||||
Foundation (<Acronym>NSF</Acronym>), and ESL, Inc.
|
||||
</Para>
|
||||
<productname>PostgreSQL</productname> is based on
|
||||
<ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html">
|
||||
<productname>Postgres release 4.2</productname></ulink>.
|
||||
The <productname>Postgres</productname> project,
|
||||
led by Professor Michael Stonebraker, was sponsored by the
|
||||
Defense Advanced Research Projects Agency (<acronym>DARPA</acronym>), the
|
||||
Army Research Office (<acronym>ARO</acronym>), the National Science
|
||||
Foundation (<acronym>NSF</acronym>), and ESL, Inc.
|
||||
</para>
|
||||
|
||||
<Sect1>
|
||||
<Title> What is <ProductName>Postgres</ProductName>?</Title>
|
||||
<sect1>
|
||||
<title> What is <productname>Postgres</productname>?</title>
|
||||
|
||||
<Para>
|
||||
Traditional relational database management systems
|
||||
(DBMSs) support a data model consisting of a collection
|
||||
of named relations, containing attributes of a specific
|
||||
type. In current commercial systems, possible types
|
||||
include floating point numbers, integers, character
|
||||
strings, money, and dates. It is commonly recognized
|
||||
that this model is inadequate for future data
|
||||
processing applications.
|
||||
The relational model successfully replaced previous
|
||||
models in part because of its "Spartan simplicity".
|
||||
However, as mentioned, this simplicity often makes the
|
||||
implementation of certain applications very difficult.
|
||||
<ProductName>Postgres</ProductName> offers substantial additional
|
||||
power by incorporating the following four additional
|
||||
basic concepts in such a way that users can easily
|
||||
extend the system:
|
||||
<para>
|
||||
Traditional relational database management systems
|
||||
(DBMSs) support a data model consisting of a collection
|
||||
of named relations, containing attributes of a specific
|
||||
type. In current commercial systems, possible types
|
||||
include floating point numbers, integers, character
|
||||
strings, money, and dates. It is commonly recognized
|
||||
that this model is inadequate for future data
|
||||
processing applications.
|
||||
The relational model successfully replaced previous
|
||||
models in part because of its "Spartan simplicity".
|
||||
However, as mentioned, this simplicity often makes the
|
||||
implementation of certain applications very difficult.
|
||||
<productname>Postgres</productname> offers substantial additional
|
||||
power by incorporating the following four additional
|
||||
basic concepts in such a way that users can easily
|
||||
extend the system:
|
||||
|
||||
<SimpleList>
|
||||
<Member>classes</Member>
|
||||
<Member>inheritance</Member>
|
||||
<Member>types</Member>
|
||||
<Member>functions</Member>
|
||||
</SimpleList>
|
||||
</Para>
|
||||
<simplelist>
|
||||
<member>classes</member>
|
||||
<member>inheritance</member>
|
||||
<member>types</member>
|
||||
<member>functions</member>
|
||||
</simplelist>
|
||||
</para>
|
||||
|
||||
<Para>
|
||||
Other features provide additional power and flexibility:
|
||||
<para>
|
||||
Other features provide additional power and flexibility:
|
||||
|
||||
<SimpleList>
|
||||
<Member>constraints</Member>
|
||||
<Member>triggers</Member>
|
||||
<Member>rules</Member>
|
||||
<Member>transaction integrity</Member>
|
||||
</SimpleList>
|
||||
</Para>
|
||||
<simplelist>
|
||||
<member>constraints</member>
|
||||
<member>triggers</member>
|
||||
<member>rules</member>
|
||||
<member>transaction integrity</member>
|
||||
</simplelist>
|
||||
</para>
|
||||
|
||||
<Para>
|
||||
These features put <ProductName>Postgres</ProductName> into the category of databases
|
||||
referred to as <FirstTerm>object-relational</FirstTerm>. Note that this is distinct
|
||||
from those referred to as <FirstTerm>object-oriented</FirstTerm>, which in general
|
||||
are not as well suited to supporting the traditional relational database languages.
|
||||
So, although <ProductName>Postgres</ProductName> has some object-oriented features,
|
||||
it is firmly in the relational database world. In fact, some commercial databases
|
||||
have recently incorporated features pioneered by <ProductName>Postgres</ProductName>.
|
||||
</Para>
|
||||
<para>
|
||||
These features put <productname>Postgres</productname> into the category of databases
|
||||
referred to as <firstterm>object-relational</firstterm>. Note that this is distinct
|
||||
from those referred to as <firstterm>object-oriented</firstterm>, which in general
|
||||
are not as well suited to supporting the traditional relational database languages.
|
||||
So, although <productname>Postgres</productname> has some object-oriented features,
|
||||
it is firmly in the relational database world. In fact, some commercial databases
|
||||
have recently incorporated features pioneered by <productname>Postgres</productname>.
|
||||
</para>
|
||||
|
||||
</Sect1>
|
||||
</sect1>
|
||||
|
||||
&history;
|
||||
&history;
|
||||
&about;
|
||||
&info;
|
||||
¬ation;
|
||||
&y2k;
|
||||
&legal;
|
||||
|
||||
&about;
|
||||
</chapter>
|
||||
|
||||
&info;
|
||||
|
||||
¬ation;
|
||||
|
||||
&y2k;
|
||||
|
||||
&legal;
|
||||
|
||||
</Chapter>
|
||||
<!-- Keep this comment at the end of the file
|
||||
Local variables:
|
||||
mode: sgml
|
||||
sgml-omittag:nil
|
||||
sgml-shorttag:t
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-always-quote-attributes:t
|
||||
sgml-indent-step:1
|
||||
sgml-indent-data:t
|
||||
sgml-parent-document:nil
|
||||
sgml-default-dtd-file:"./reference.ced"
|
||||
sgml-exposed-tags:nil
|
||||
sgml-local-catalogs:"/usr/lib/sgml/CATALOG"
|
||||
sgml-local-ecat-files:nil
|
||||
End:
|
||||
-->
|
||||
|
Reference in New Issue
Block a user