{"id":1275,"date":"2023-04-14T09:56:16","date_gmt":"2023-04-14T08:56:16","guid":{"rendered":"https:\/\/blogs.glowscotland.org.uk\/es\/software\/?page_id=1275"},"modified":"2023-08-28T10:27:19","modified_gmt":"2023-08-28T09:27:19","slug":"sql","status":"publish","type":"page","link":"https:\/\/blogs.glowscotland.org.uk\/es\/software\/data-modelling\/sql\/","title":{"rendered":"SQL"},"content":{"rendered":"\n

In the last chapter when making the form look nicer you saw the row source that looked like:<\/p>\n\n\n\n

SELECT [Vehicle].[ID], [Vehicle].[Number Plate], [Vehicle].[Manufacturer], [Vehicle].[Model] FROM [Vehicle] ORDER BY [Manufacturer], [Model], [Number Plate];<\/code><\/pre>\n\n\n\n
These SELECT, FROM and ORDER BY keywords are SQL. SQL stands for Structured Query Language.<\/p>\n\n\n\n
SQL is designed to query data stored in a relational database.<\/p>\n\n\n\n
SQL implementations are similar but not 100% compatible. The syntax you use for MS Access will not be identical to what you would need for MySQL for example.<\/p>\n\n\n\n
\n\n\n\n
Constraints<\/h2>\n\n\n\n
Constraints specify rules for the data in a table. The following are common constraints.<\/p>\n\n\n\n
CONSTRAINT<\/strong><\/td>MEANING<\/strong><\/td><\/tr>
NOT NULL<\/td>Entry cannot be left empty<\/td><\/tr>
UNIQUE<\/td>Entry must be difference from any other in the column<\/td><\/tr>
PRIMARY KEY<\/td>Combination of NOT NULL and UNIQUE<\/td><\/tr>
FOREIGN KEY<\/td>Prevents data being added if this value does not appear in the other table<\/td><\/tr>
DEFAULT<\/td>Sets a value if none given<\/td><\/tr>
CHECK<\/td>Specify conditions that need to be matched to be valid<\/td><\/tr><\/tbody><\/table>
Common constraints<\/figcaption><\/figure>\n\n\n\n
Simple constraints can be added after the column definition in a CREATE or ALTER statement e.g.<\/p>\n\n\n\n
CREATE TABLE Test (ID int PRIMARY KEY, ...<\/code><\/pre>\n\n\n\n
Alternatively, or with more complex ones dealing with multiple columns, you add a CONSTRAINT line to the end of the query.<\/p>\n\n\n\n
...\nAge int,\nCONSTRAINT CHK_Age (Age >= 18 AND Age <= 100)...<\/code><\/pre>\n\n\n\n
\n\n\n\n
Data types<\/h2>\n\n\n\n
Up until now you have dealt with either a high level design data type such as Number where Number is any numeric value, or in Access where Number is an small integer by default. In SQL you state the exact data type when creating or altering a table. The most common ones are:<\/p>\n\n\n\n
DATA TYPE<\/strong><\/td>DESCRIPTION<\/strong><\/td><\/tr>
SHORT or INT<\/td>Whole number between -32768 and 32767<\/td><\/tr>
LONG<\/td>Whole number between -2147483648 and 2147483647<\/td><\/tr>
SINGLE<\/td>Single precision floating point number<\/td><\/tr>
DOUBLE<\/td>Double precision floating point number<\/td><\/tr>
VARCHAR(n)<\/td>Variable width character string, where n is the max length. n cannot be more than 8000 max characters<\/td><\/tr>
TINYINT(1) or BIT<\/td>0, 1 or NULL used for boolean<\/td><\/tr>
DATETIME<\/td>Store a date and time in ithe format YYYY-MM-DD hh:mm:ss<\/td><\/tr><\/tbody><\/table>
Common data types<\/figcaption><\/figure>\n\n\n\n
\n\n\n\n
Reserved words<\/h2>\n\n\n\n
Just like in programming, some words are reserved and must be escaped before they can be used. Each SQL platform is different so search the documentation if you encounter one.<\/p>\n\n\n\n
For example, in MySQL you escape a table or column name by enclosing it in backticks, the ` character to the left of the 1 key. Whereas in Access you use the square brackets.<\/p>\n\n\n\n
\n\n\n\n
Creating a database<\/h2>\n\n\n\n
There are normally two parts to creating a database:<\/p>\n\n\n\n
    \n
  • Create the database<\/li>\n\n\n\n
  • Grant access to one or more users<\/li>\n<\/ul>\n\n\n\n
    In simplest terms, granting one user the same permissions to all tables, for MySQL you would use syntax like:<\/p>\n\n\n\n
    CREATE DATABASE databasename DEFAULT CHARSET charset;\nGRANT permissions ON databasename.* TO 'username'@'hostname' IDENTIFIED BY 'password';<\/code><\/pre>\n\n\n\n
    Where databasename, charset, permissions, username, hostname and password are all replaced by relevant values e.g.<\/p>\n\n\n\n
    CREATE DATABASE db_hotel_guests DEFAULT CHARSET utf8;\nGRANT ALL ON db_hotel_guests.* TO 'hotel_admin'@'localhost' IDENTIFIED BY 'j)ks89KIos0Kle,31d';<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    Creating a table<\/h2>\n\n\n\n
    The CREATE TABLE query gives the table a name and then lists the column names, their data type and any constraints e.g.<\/p>\n\n\n\n
    CREATE TABLE TestLink (\n`ID` INT NOT NULL PRIMARY KEY,\n`Name` VARCHAR(100) NOT NULL,\n`DriverID` INT,\nCONSTRAINT FK_DriverTestLink FOREIGN KEY (`DriverID`) REFERENCES Driver(`ID`)\n);<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    Inserting data<\/h2>\n\n\n\n
    To add a new row to a table you use the INSERT INTO command following the format:<\/p>\n\n\n\n
    INSERT INTO TableName VALUES (Value1, Value2\u2026);<\/p>\n\n\n\n
    For example:<\/p>\n\n\n\n
    INSERT INTO Driver VALUES (0000000001, 'John', 'Doe', '123 Main Street', 01234567890, 'jdoe@example.com');<\/code><\/pre>\n\n\n\n
    Some RDBMS allow you to list which columns you want to supply data for. But you would need to include any required field unless they are a field automatically filled by the database such as when using the DEFAULT constraint e.g.<\/p>\n\n\n\n
    INSERT INTO Driver (Forename, Surname, Address) VALUES ('John', 'Doe', '123 Main Street');<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    Selecting data<\/h2>\n\n\n\n
    The SELECT \u2026 FROM statement is used to select data from a database.<\/p>\n\n\n\n
    To select all the records from a table you use an asterisk (*) instead of a column name. For example, to get all the drivers in the Driver table you could use the following SQL:<\/p>\n\n\n\n
    SELECT * FROM Driver;<\/code><\/pre>\n\n\n\n
    To only view certain columns in the results you replace the * with the column names e.g.<\/p>\n\n\n\n
    SELECT Forename, Surname FROM Driver;<\/code><\/pre>\n\n\n\n
    SELECT \u2026 FROM \u2026 WHERE Queries<\/h3>\n\n\n\n
    By adding a WHERE clause to the query you can limit the results to only those that match. For example:<\/p>\n\n\n\n
    SELECT * FROM Driver WHERE Surname = 'Smith';<\/code><\/pre>\n\n\n\n
    Will return all the columns in the Driver table but only for the rows that have a value of  \u2018Smith\u2019 in the Surname column.<\/p>\n\n\n\n
    \n\n\n\n
    Operators<\/h2>\n\n\n\n
    WHERE queries can be refined using operators. In the previous slide we used = to return matching values. But you can also use > and < for checking greater than and less than comparisons of numeric data e.g.<\/p>\n\n\n\n
    SELECT ID FROM Invoice WHERE Amount > 500;<\/code><\/pre>\n\n\n\n
    Queries can be further refined using the AND and OR operators:<\/p>\n\n\n\n
      \n
    • AND will only return a row where both sides of the AND operator are true<\/li>\n\n\n\n
    • OR will only return a row where either side of the OR operator is true<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n
      Ordering the results<\/h2>\n\n\n\n
      The ORDER BY clause is used to order the results by the given column in the given order. The order being either ascending (ASC) or descending (DESC) e.g.<\/p>\n\n\n\n
      SELECT Forename, Surname FROM Driver ORDER BY Forename ASC;<\/code><\/pre>\n\n\n\n
      You can also order by multiple columns e.g.<\/p>\n\n\n\n
      SELECT Forename, Surname FROM Driver ORDER BY Forename ASC, Surname ASC;<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      Wildcards<\/h2>\n\n\n\n
      Wildcard characters are used with the SQL operator LIKE when you want to match only part of a string or text.<\/p>\n\n\n\n
        \n
      • % denotes a set of characters<\/li>\n\n\n\n
      • _ denotes a single character<\/li>\n<\/ul>\n\n\n\n
        For MS Access use:<\/p>\n\n\n\n
          \n
        • * instead of %<\/li>\n\n\n\n
        • ? instead of _<\/li>\n<\/ul>\n\n\n\n
          For a=example, to find all the rows of the Driver table where the Surname field begins with Mac you could use a query like:<\/p>\n\n\n\n
          SELECT * FROM Driver WHERE Surname LIKE 'Mac%';<\/code><\/pre>\n\n\n\n
          \n\n\n\n
          Updating entries<\/h2>\n\n\n\n
          To edit the data that already exists in a database you use the UPDATE query. This follows the format:<\/p>\n\n\n\n
          UPDATE TableName SET ColumnName = Value;<\/code><\/pre>\n\n\n\n
          But you will almost always<\/strong> use a WHERE clause to limit the number of rows being changed.<\/p>\n\n\n\n
          UPDATE TableName SET ColumnName = NewValue WHERE ColumnToMatch = ValueToMatch;<\/code><\/pre>\n\n\n\n
          For example:<\/p>\n\n\n\n
          UPDATE Driver SET Address = 'Flat 1, 123 Main Street' WHERE ID = 0000000001;<\/code><\/pre>\n\n\n\n
          This will only change the record with that ID even if there is another driver called John Doe living at 123 Main Street.<\/p>\n\n\n\n
          \n\n\n\n
          Deleting entries<\/h2>\n\n\n\n
          To remove data from a table you use the DELETE query in the format:<\/p>\n\n\n\n
          DELETE FROM TableName;<\/code><\/pre>\n\n\n\n
          You should always<\/strong> use a WHERE clause to limit the rows affected:<\/p>\n\n\n\n
          DELETE FROM TableName WHERE ColumnToMatch = ValueToMatch;<\/code><\/pre>\n\n\n\n
          \n\n\n\n
          Joining tables<\/h2>\n\n\n\n
          Joins are used to combine the columns from multiple tables into the results of a single query. The most common is the inner join.<\/p>\n\n\n\n
          An INNER JOIN clause is used to select data from more than one table.<\/p>\n\n\n\n
          SELECT Driver.Forename, Driver.Surname, Invoice.CreatedDate, Invoice.Amount\nFROM Driver\nINNER JOIN Invoice on Driver.ID = Invoice.DriverID\nWHERE Invoice.Paid = false;<\/code><\/pre>\n\n\n\n
          You can still use WHERE and ORDER BY clauses with inner joins. The join is simply to combine multiple tables into one temporary table for the purpose of the query.<\/p>\n\n\n\n
          \n\n\n\n
          Functions<\/h2>\n\n\n\n
          Most RDBMS come with built in functions that can be used in a SELECT statement. Some common functions are:<\/p>\n\n\n\n
          FUNCTION NAME<\/strong><\/td>MEANING<\/strong><\/td><\/tr>
          AVG()<\/td>Returns the average value of a numeric column or expression<\/td><\/tr>
          COUNT()<\/td>Returns the number of rows that match the criteria in the WHERE clause<\/td><\/tr>
          MAX()<\/td>Returns the largest value of the selected column or expression<\/td><\/tr>
          MIN()<\/td>Returns the smallest value of the selected column or expression<\/td><\/tr>
          SUM()<\/td>Returns the total sum of a numeric column or expression<\/td><\/tr>
          FORMAT()<\/td>Format a value to a given pattern, such as setting the number of decimal places<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
          Common rdbms functions<\/p>\n\n\n\n
          Use self learning to find how to use these functions with the database product that you are using. While most are similar, there might be differences between products. Check to be sure.<\/p>\n\n\n\n
          Because the function returns a single value for the whole column you cannot mix it with a regular select column that would return multiple rows.<\/p>\n\n\n\n
          SELECT ID, MAX(Amount) FROM Invoice;<\/code><\/pre>\n\n\n\n
          You can use it in a select statement that contains multiple functions as they each only return one vale.<\/p>\n\n\n\n
          SELECT COUNT(ID), MAX(Amount) FROM Invoice;<\/code><\/pre>\n\n\n\n
          \n\n\n\n
          Aliases<\/h2>\n\n\n\n
          Aliases allow you to use a different name in your queries from the given table or column name. This is useful if you are dealing with really long names, ambiguous names, or computed column names formed when creating a column from a mathematical equation of other columns.<\/p>\n\n\n\n
          Long name example:<\/p>\n\n\n\n
          SELECT DriverID As ['dID'], VehicleID As ['vID'] FROM DriverVehicleLink As['DVl'];<\/code><\/pre>\n\n\n\n
          Ambiguous name example:<\/p>\n\n\n\n
          SELECT * FROM Table3458687687 As ['FeedbackJune21'];<\/code><\/pre>\n\n\n\n
          Computed name example:<\/p>\n\n\n\n
          SELECT StartingBalance - Costs As ['CurrentBalance'] FROM PettyCash;<\/code><\/pre>\n\n\n\n
          \n\n\n\n
          Grouping results<\/h2>\n\n\n\n
          The GROUP BY clause groups rows of records together that are identical based on the criteria given. This is useful because you run functions on these groups rather than the entire column e.g.<\/p>\n\n\n\n
          SELECT COUNT(Make), Make FROM Vehicle GROUP BY Make;<\/code><\/pre>\n\n\n\n
          +-------------------------------+\n| COUNT(Make)       | Make      |\n+-------------------------------+\n|                  3| Ford      |\n|                  5| Renault   |\n|                  1| Tesla     |\n+-------------------------------+<\/code><\/pre>\n\n\n\n
          You can use ORDER BY and GROUP BY clauses in the same query but the GROUP BY must come before the ORDER BY.<\/p>\n\n\n\n
          \n\n\n\n
          How to see the SQL in Access<\/h2>\n\n\n\n
          Click the Create Menu and choose the Query Wizard option. Then choose the \u201cSimple Query Wizard\u201d in the popup.<\/p>\n\n\n\n
          Use the arrows on the next page to add all the columns to the right-hand box then click Next.<\/p>\n\n\n\n
          Choose a name for the query and choose the Modify option before clicking finish.<\/p>\n\n\n
          \n
          \"Simple
          Simple Query Wizard button location<\/figcaption><\/figure><\/div>\n\n\n
          On the far left of the Design Ribbon is an option for View. Click this the in the dropdown choose \u201cSQL View\u201d.<\/p>\n\n\n\n
          You can now create SQL statements. To run the query, click the Run option in the Design ribbon.<\/p>\n\n\n\n
          If the table that you are adding data to is open, you will need to close and reopen it to see the new data.<\/p>\n\n\n
          \n
          \"SQL
          SQL View option location<\/figcaption><\/figure><\/div>\n\n\n
          \n\n\n\n
          Syntax errors<\/h2>\n\n\n\n
          As mentioned above, some words are reserved and must be escaped before they can be used. In Access you should surround the word in square brackets [] or rename that column or table.<\/p>\n\n\n\n
          If you used a column called Note in the previous slide you will have encountered a syntax error when you tried to run the query and Access will have highlighted the word causing the issue. Try escaping it in square brackets [Note].<\/p>\n","protected":false},"excerpt":{"rendered":"
          In the last chapter when making the form look nicer you saw the row source that looked like: These SELECT, FROM and ORDER BY keywords are SQL. SQL stands for Structured Query Language. SQL is designed to query data stored in a relational database. SQL implementations are similar but not 100% compatible. The syntax you… Continue reading SQL<\/span><\/a><\/p>\n","protected":false},"author":5710,"featured_media":0,"parent":1179,"menu_order":6,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-1275","page","type-page","status-publish","hentry","entry"],"_links":{"self":[{"href":"https:\/\/blogs.glowscotland.org.uk\/es\/software\/wp-json\/wp\/v2\/pages\/1275","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.glowscotland.org.uk\/es\/software\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/blogs.glowscotland.org.uk\/es\/software\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.glowscotland.org.uk\/es\/software\/wp-json\/wp\/v2\/users\/5710"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.glowscotland.org.uk\/es\/software\/wp-json\/wp\/v2\/comments?post=1275"}],"version-history":[{"count":3,"href":"https:\/\/blogs.glowscotland.org.uk\/es\/software\/wp-json\/wp\/v2\/pages\/1275\/revisions"}],"predecessor-version":[{"id":1353,"href":"https:\/\/blogs.glowscotland.org.uk\/es\/software\/wp-json\/wp\/v2\/pages\/1275\/revisions\/1353"}],"up":[{"embeddable":true,"href":"https:\/\/blogs.glowscotland.org.uk\/es\/software\/wp-json\/wp\/v2\/pages\/1179"}],"wp:attachment":[{"href":"https:\/\/blogs.glowscotland.org.uk\/es\/software\/wp-json\/wp\/v2\/media?parent=1275"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}