[development] Supporting PostgreSQL schema level

Jean-Michel Pouré jm at poure.com
Thu Jan 17 17:33:12 UTC 2008

On jeu, 2008-01-17 at 08:56 -0800, Jason Flatt wrote:
> I don't know if it provides what you are referring to, or if you're
> using the 
> same term to describe something different, but in Drupal 6, there is a
> new 
> Schema API: http://drupal.org/node/146843

It is not the same.

I was refering to PostgreSQL schema :

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. 

More information about the development mailing list