📑 Table of Contents

The SQL/Schemata, or Information and Definition Schemas, part of the SQL standard is defined by ISO/IEC 9075-11:2008. SQL/Schemata defines the information schema and definition schema, providing a common set of tools to make SQL databases and objects self-describing. These tools include the SQL object identifier[clarification needed], structure[clarification needed] and integrity constraints, security and authorization specifications[clarification needed], features and packages[clarification needed] of ISO/IEC 9075, support of features provided by SQL-based DBMS implementations, SQL-based DBMS implementation information and sizing items[clarification needed], and the values supported[clarification needed] by the DBMS implementations.[1] SQL/Schemata defines a number of features, some of which are mandatory.

See also

edit

References

edit
  1. ^ ISO/IEC 9075-11:2008: Information and Definition Schemas (SQL/Schemata), 2008, p. 1
edit


📚 Artikel Terkait di Wikipedia

Data definition language

tables to query schemas. These information tables were specified as SQL/Schemata in SQL:2003. The term DDL is also used in a generic sense to refer to any

SQL

criteria. This is an important element of SQL. Statements, which may have a persistent effect on schemata and data, or may control transactions, program

SQL syntax

criteria. This is an important element of SQL. Statements, which may have a persistent effect on schemata and data, or may control transactions, program

Object–relational impedance mismatch

schemata. Frameworks leverage referential integrity constraints and other schema information to standardize handling away from case-by-case code. SQL

Metadata

intelligence or "inferencing" occurring, just the illusion thereof. Metadata schemata can be hierarchical in nature where relationships exist between metadata

Elementary key normal form

(September 1982). "A New Normal Form for the Design of Relational Database Schemata" (PDF). ACM Transactions on Database Systems. 7 (3): 489–499. doi:10.1145/319732

Third normal form

defined by English computer scientist Edgar F. Codd. A relation (or table, in SQL) is in third normal form if it is in second normal form and also lacks non-key

IDEF1X

are: External schema for user views Conceptual schema integrates external schemata Internal schema that defines physical storage structures. At the center