{
  "id": "enwiki-001375240833",
  "slug": "sql-syntax",
  "title": "SQL syntax",
  "qid": "",
  "lead": "The syntax of the SQL programming language is defined and maintained by ISO/IEC SC 32 as part of ISO/IEC 9075. This standard is not freely available. Despite the existence of the standard, SQL code is not completely portable among different database systems without adjustments.",
  "body": "The syntax of the SQL programming language is defined and maintained by ISO/IEC SC 32 as part of ISO/IEC 9075. This standard is not freely available. Despite the existence of the standard, SQL code is not completely portable among different database systems without adjustments. {{Image frame|content= \\left. \\begin{array}{rl} \\scriptstyle\\mathtt{UPDATE~clause} & \\{ \\mathtt{UPDATE\\ country} \\\\ \\scriptstyle\\mathtt{SET~clause} & \\{ \\mathtt{SET\\ population =~} \\overbrace\\mathtt{population + 1}^\\mathtt{expression} \\\\ \\scriptstyle\\mathtt{WHERE~clause} & \\{ \\mathtt{WHERE\\ \\underbrace{{name =} \\overbrace{'USA'}^{expression}}_{predicate};} \\end{array} \\right\\}{\\scriptstyle\\texttt{statement}} |width=500|caption=A chart showing several of the SQL language elements that compose a single statement. This adds one to the population of the USA in the country table.}} The SQL language is subdivided into several language elements, including: Keywords are words that are defined in the SQL language. They are either reserved (e.g. , and ), or non-reserved (e.g. , and ). List of SQL reserved words. Identifiers are names on database objects, like tables, columns and schemas. An identifier may not be equal to a reserved keyword, unless it is a delimited identifier. Delimited identifiers means identifiers enclosed in double quotation marks. They can contain characters normally not supported in SQL identifiers, and they can be identical to a reserved word, e.g. a column named is specified as . In MySQL, double quotes are string literal delimiters by default instead. Enabling the SQL mode enforces the SQL standard behavior. These can also be used regardless of this mode through backticks: . Clauses, which are constituent components of statements and queries. (In some cases, these are optional.) Expressions, which can produce either scalar values, or tables consisting of columns and rows of data Predicates, which specify conditions that can be evaluated to SQL three-valued logic (3VL) (true/false/unknown) or Boolean truth values and are used to limit the effects of statements and queries, or to change program flow. Queries, which retrieve the data based on specific criteria. This is an important element of SQL. Statements, which may have a persistent effect on schemata and data, or may control transactions, program flow, connections, sessions, or diagnostics. SQL statements also include the semicolon (\";\") statement terminator. Though not required on every platform, it is defined as a standard part of the SQL grammar. Insignificant whitespace is generally ignored in SQL statements and queries, making it easier to format SQL code for readability. CASE WHEN n > 0 THEN 'positive' WHEN n SQL tests conditions in the order they appear in the source. If the source does not specify an expression, SQL defaults to . An abbreviated syntax called \"simple case\" can also be used: CASE n WHEN 1 THEN 'One' WHEN 2 THEN 'Two' ELSE 'I cannot count that high' END This syntax uses implicit equality comparisons, with the usual caveats for comparing with NULL. There are two short forms for special expressions: and . The expression returns the value of the first non-NULL operand, found by working from left to right, or NULL if all the operands equal NULL. COALESCE(x1,x2) is equivalent to: CASE WHEN x1 IS NOT NULL THEN x1 ELSE x2 END The expression has two operands and returns NULL if the operands have the same value, otherwise it has the value of the first operand. NULLIF(x1, x2) is equivalent to CASE WHEN x1 = x2 THEN NULL ELSE x1 END SELECT * FROM Book WHERE price > 100.00 ORDER BY title; The example below demonstrates a query of multiple tables, grouping, and aggregation, by returning a list of books and the number of authors associated with each book. SELECT Book.title AS Title, count(*) AS Authors FROM Book JOIN Book_author ON Book.isbn = Book_author.isbn GROUP BY Book.title; Example output might resemble the following: Title Authors ---------------------- ------- SQL Examples and Guide 4 The Joy of SQL 1 An Introduction to SQL 2 Pitfalls of SQL 1 Under the precondition that isbn is the only common column name of the two tables and that a column named title only exists in the Book table, one could re-write the query above in the following form: SELECT title, count(*) AS Authors FROM Book NATURAL JOIN Book_author GROUP BY title; However, many vendors either do not support this approach, or require certain column-naming conventions for natural joins to work effectively. SQL includes operators and functions for calculating values on stored values. SQL allows the use of expressions in the select list to project data, as in the following example, which returns a list of books that cost more than 100.00 with an additional sales_tax column containing a sales tax figure calculated at 6% of the price. SELECT isbn, title, price, price * 0.06 AS sales_tax FROM Book WHERE price > 100.00 ORDER BY title; SELECT isbn, title, price FROM Book WHERE price A subquery can use values from the outer query, in which case it is known as a correlated subquery. Since 1999 the SQL standard allows clauses for subqueries, i.e. named subqueries, usually called common table expressions (also called subquery factoring). CTEs can also be recursive by referring to themselves; the resulting mechanism allows tree or graph traversals (when represented as relations), and more generally fixpoint computations. SELECT b.isbn, b.title, b.price, sales.items_sold, sales.company_nm FROM Book b JOIN (SELECT SUM(Items_Sold) Items_Sold, Company_Nm, ISBN FROM Book_Sales GROUP BY Company_Nm, ISBN) sales ON sales.isbn = b.isbn The concept of Null allows SQL to deal with missing information in the relational model. The word is a reserved keyword in SQL, used to identify the Null special marker. Comparisons with Null, for instance equality (=) in WHERE clauses, results in an Unknown truth value. In SELECT statements SQL returns only results for which the WHERE clause returns a value of True; i.e., it excludes results with values of False and also excludes those whose value is Unknown. Along with True and False, the Unknown resulting from direct comparisons with Null thus brings a fragment of three-valued logic to SQL. The truth tables SQL uses for AND, OR, and NOT correspond to a common fragment of the Kleene and Lukasiewicz three-valued logic (which differ in their definition of implication, however SQL defines no such operation). | valign=\"top\" | |} | valign=\"top\" | |} There are however disputes about the semantic interpretation of Nulls in SQL because of its treatment outside direct comparisons. As seen in the table above, direct equality comparisons between two NULLs in SQL (e.g. ) return a truth value of Unknown. This is in line with the interpretation that Null does not have a value (and is not a member of any data domain) but is rather a placeholder or \"mark\" for missing information. However, the principle that two Nulls aren't equal to each other is effectively violated in the SQL specification for the and operators, which do identify nulls with each other. Consequently, these set operations in SQL may produce results not representing sure information, unlike operations involving explicit comparisons with NULL (e.g. those in a clause discussed above). In Codd's 1979 proposal (which was basically adopted by SQL92) this semantic inconsistency is rationalized by arguing that removal of duplicates in set operations happens \"at a lower level of detail than equality testing in the evaluation of retrieval operations\". However, computer-science professor Ron van der Meyden concluded that \"The inconsistencies in the SQL standard mean that it is not possible to ascribe any intuitive logical semantics to the treatment of nulls in SQL.\" Additionally, because SQL operators return Unknown when comparing anything with Null directly, SQL provides two Null-specific comparison predicates: and test whether data is or is not Null. SQL does not explicitly support universal quantification, and must work it out as a negated existential quantification. There is also the infixed comparison operator, which returns TRUE unless both operands are equal or both are NULL. Likewise, IS NOT DISTINCT FROM is defined as . SQL:1999 also introduced data type, which according to the standard can also hold Unknown values if it is nullable. In practice, a number of systems (e.g. PostgreSQL) implement the BOOLEAN Unknown as a BOOLEAN NULL, which the standard says that the NULL BOOLEAN and UNKNOWN \"may be used interchangeably to mean exactly the same thing\". INSERT INTO example (column1, column2, column3) VALUES ('test', 'N', NULL); modifies a set of existing table rows, e.g.: UPDATE example SET column1 = 'updated value' WHERE column2 = 'N'; removes existing rows from a table, e.g.: DELETE FROM example WHERE column2 = 'N'; is used to combine the data of multiple tables. It combines the and elements. It is defined in the SQL:2003 standard; prior to that, some databases provided similar functionality via different syntax, sometimes called \"upsert\". MERGE INTO table_name USING table_reference ON (condition) WHEN MATCHED THEN UPDATE SET column1 = value1 [, column2 = value2 ...] WHEN NOT MATCHED THEN INSERT (column1 [, column2 ...]) VALUES (value1 [, value2 ...]) CREATE TABLE tbl_1(id int); INSERT INTO tbl_1(id) VALUES(1); INSERT INTO tbl_1(id) VALUES(2); COMMIT; UPDATE tbl_1 SET id=200 WHERE id=1; SAVEPOINT id_1upd; UPDATE tbl_1 SET id=1000 WHERE id=2; ROLLBACK to id_1upd; SELECT id from tbl_1; COMMIT makes all data changes in a transaction permanent. ROLLBACK discards all data changes since the last or , leaving the data as it was prior to those changes. Once the statement completes, the transaction's changes cannot be rolled back. and terminate the current transaction and release data locks. In the absence of a or similar statement, the semantics of SQL are implementation-dependent. The following example shows a classic transfer of funds transaction, where money is removed from one account and added to another. If either the removal or the addition fails, the entire transaction is rolled back. START TRANSACTION; UPDATE Account SET amount=amount-200 WHERE account_number=1234; UPDATE Account SET amount=amount+200 WHERE account_number=2345; IF ERRORS=0 COMMIT; IF ERRORS<>0 ROLLBACK; CREATE TABLE example( column1 INTEGER, column2 VARCHAR(50), column3 DATE NOT NULL, PRIMARY KEY (column1, column2) ); ALTER modifies the structure of an existing object in various ways, for example, adding a column to an existing table or a constraint, e.g.: ALTER TABLE example ADD column4 INTEGER DEFAULT 25 NOT NULL; TRUNCATE deletes all data from a table in a very fast way, deleting the data inside the table and not the table itself. It usually implies a subsequent COMMIT operation, i.e., it cannot be rolled back (data is not written to the logs for rollback later, unlike DELETE). TRUNCATE TABLE example; DROP deletes an object in the database, usually irretrievably, i.e., it cannot be rolled back, e.g.: DROP TABLE example; GRANT SELECT, UPDATE ON example TO some_user, another_user; REVOKE SELECT, UPDATE ON example FROM some_user, another_user; ==References== ==External links== . .",
  "categories": [
    "20483874",
    "22911297",
    "22961501",
    "23204648",
    "23603337",
    "24745122",
    "26220375",
    "29815557",
    "31128808",
    "31128809",
    "33410312",
    "39691157",
    "59428581",
    "72914727"
  ],
  "license": "CC BY-SA 4.0",
  "source_uri": "https://en.wikipedia.org/w/index.php?oldid=1375240833",
  "content_hash": "",
  "created_at": null,
  "updated_at": 1789570372.0,
  "claims": [],
  "contradictions": [],
  "confidence": 0.6,
  "csl": {
    "id": "enwiki-001375240833",
    "type": "webpage",
    "title": "SQL syntax",
    "author": [
      {
        "family": "Anticloud FZ LLE",
        "literal": "Anticloud FZ LLE"
      }
    ],
    "container-title": "encyclopegia.org",
    "publisher": "Anticloud FZ LLE",
    "publisher-place": "Dubai, United Arab Emirates",
    "URL": "https://encyclopegia.org/a/sql-syntax",
    "issued": {
      "date-parts": [
        [
          2026,
          11,
          18
        ]
      ]
    },
    "accessed": {
      "date-parts": [
        [
          2026,
          11,
          18
        ]
      ]
    },
    "license": "CC BY-SA 4.0",
    "DOI": "eo1:enwiki-001375240833",
    "isBasedOn": "https://en.wikipedia.org/w/index.php?oldid=1375240833",
    "note": "Immutable snapshot enwiki-001375240833"
  }
}