[development] Supporting PostgreSQL schema level

[Earnie Boyd]

Quoting Jean-Michel Pouré <jm at poure.com>:

> I was refering to PostgreSQL schema :
> http://www.postgresql.org/docs/8.2/static/ddl-schemas.html
>
> database contains one or more named schemas, which in turn contain
> tables. Schemas also contain other kinds of named objects, including
> data types, functions, and operators. The same object name can be used
> in different schemas without conflict; for example, both schema1 and
> myschema may contain tables named mytable. Unlike databases, schemas are
> not rigidly separated: a user may access objects in any of the schemas
> in the database he is connected to, if he has privileges to do so.
>
> There are several reasons why one might want to use schemas:
>
>      * To allow many users to use one database without interfering with
>        each other.
>
>      * To organize database objects into logical groups to make them
>        more manageable.
>
>      * Third-party applications can be put into separate schemas so
>        they cannot collide with the names of other objects.
>
>
> Schemas are analogous to directories at the operating system level,
> except that schemas cannot be nested.
>

BTW, Oracle has something similar.  Think of them sub-databases 
contained within the same database file sets.  You have different table 
objects containing different sets of data but described the same way 
and the table objects have different users.

Earnie -- http://for-my-kids.com/
-- http://give-me-an-offer.com/