Difference between revisions of "Database Schema"

From wikieduonline
Jump to navigation Jump to search
Line 6: Line 6:
 
* To organize database objects into logical groups to make them more manageable.
 
* To organize database objects into logical groups to make them more manageable.
 
* Third-party applications can be put into separate schemas so they do not collide with the names of other objects.
 
* Third-party applications can be put into separate schemas so they do not collide with the names of other objects.
 +
 +
 +
[[PostgreSQL]]:
 +
* Show/List [[schema]]s: <code>select nspname from pg_catalog.pg_namespace;</code><ref>https://dba.stackexchange.com/questions/40045/how-do-i-list-all-schemas-in-postgresql</ref>
 +
 +
  
 
== See also ==
 
== See also ==

Revision as of 13:22, 15 June 2020

Database schemas are analogous to directories at the operating system level, except that schemas cannot be nested. [1]


Typical schemas usage scenarios:

  • 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 do not collide with the names of other objects.


PostgreSQL:

  • Show/List schemas: select nspname from pg_catalog.pg_namespace;[2]


See also

  • https://www.postgresql.org/docs/current/ddl-schemas.html
  • https://dba.stackexchange.com/questions/40045/how-do-i-list-all-schemas-in-postgresql
  • Advertising: