| Both sides previous revision Previous revision | |
| dido:99_annexes:annex-b-terms-and-definitions:s:sql [2026/07/11 11:14] – ↷ Links adapted because of a move operation nick_dido | dido:99_annexes:annex-b-terms-and-definitions:s:sql [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| Structured Query Language (SQL) provides a standard language for defining, querying, manipulating, and controlling data in relational database systems. | Structured Query Language (SQL) provides a standard language for defining, querying, manipulating, and controlling data in relational database systems. |
| |
| SQL supports database schemas, tables, columns, [[dido:99_annexes:annex-b-terms-and-definitions:d:datatype| datatypes]], constraints, queries, views, transactions, access control, and stored logic. In architecture work, SQL artefacts express semantic content when table names, column names, constraints, relationships, views, and queries preserve [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to defined domain meaning. | SQL supports database schemas, tables, columns, [[dido:99_annexes:annex-b-terms-and-definitions:d:datatype| datatypes]], constraints, queries, views, transactions, access control, and stored logic. In architecture work, SQL artifacts express semantic content when table names, column names, constraints, relationships, views, and queries preserve [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to defined domain meaning. |
| |
| SQL differs from [[dido:99_annexes:annex-b-terms-and-definitions:s:schema|schema]]. A schema defines information elements, permitted values, relationships, and constraints within a defined representation context. SQL provides one language for defining and using database schemas in relational database environments. | SQL differs from [[dido:99_annexes:annex-b-terms-and-definitions:s:schema|schema]]. A schema defines information elements, permitted values, relationships, and constraints within a defined representation context. SQL provides one language for defining and using database schemas in relational database environments. |
| |
| SQL also differs from [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic]]. SQL syntax and database structure do not establish domain meaning on their own. SQL expresses selected semantic content when SQL artefacts trace to a [[dido:99_annexes:annex-b-terms-and-definitions:c:conceptual_model|conceptual model]], vocabulary, [[dido:99_annexes:annex-b-terms-and-definitions:t:type_system|type system]], rule set, report model, or other authoritative semantic source. | SQL also differs from [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic]]. SQL syntax and database structure do not establish domain meaning on their own. SQL expresses selected semantic content when SQL artifacts trace to a [[dido:99_annexes:annex-b-terms-and-definitions:c:conceptual_model|conceptual model]], vocabulary, [[dido:99_annexes:annex-b-terms-and-definitions:t:type_system|type system]], rule set, report model, or other authoritative semantic source. |
| |
| SQL semantic content includes: | SQL semantic content includes: |
| ===== Source ===== | ===== Source ===== |
| |
| Generalised from ISO/IEC 9075 SQL usage, relational database practice, data modelling practice, and software architecture usage; specialised for use in the FX Demo Reference Architecture. | Generalised from ISO/IEC 9075 SQL usage, relational database practice, data modeling practice, and software architecture usage; specialized for use in the FX Demo Reference Architecture. |
| |
| ===== Note ===== | ===== Note ===== |
| |
| SQL is not equivalent to a conceptual model, schema, ontology, or semantic model. SQL artefacts express selected semantic commitments in a relational database context when their structures, constraints, and queries preserve traceability to governed domain meaning. | SQL is not equivalent to a conceptual model, schema, ontology, or semantic model. SQL artifacts express selected semantic commitments in a relational database context when their structures, constraints, and queries preserve traceability to governed domain meaning. |
| |
| A database column can have a valid SQL datatype while still lacking clear domain meaning. For example, a column with datatype ''DATE'' does not by itself distinguish ''tradeDate'', ''settlementDate'', ''effectiveDate'', or ''terminationDate''. | A database column can have a valid SQL datatype while still lacking clear domain meaning. For example, a column with datatype ''DATE'' does not by itself distinguish ''tradeDate'', ''settlementDate'', ''effectiveDate'', or ''terminationDate''. |
| An FX trade table defines selected relational structures for trade information. | An FX trade table defines selected relational structures for trade information. |
| |
| ^ SQL artefact ^ Example ^ Semantic interpretation ^ | ^ SQL artifact ^ Example ^ Semantic interpretation ^ |
| | Table | ''FX_TRADE'' | relational representation of FX trade records | | | Table | ''FX_TRADE'' | relational representation of FX trade records | |
| | Column | ''TRADE_IDENTIFIER'' | identifier for the trade | | | Column | ''TRADE_IDENTIFIER'' | identifier for the trade | |