Create and Populate Database Table with Mysql Workbench

Total Page:16

File Type:pdf, Size:1020Kb

Create and Populate Database Table with Mysql Workbench Create and Populate a Database Table with MySQL Workbench Dr. Demuynck Table of Content • Slide 3: • An annotated view of the MySQL script environment • Code to create a temporary database, use the database and create a single table • Slide 4: Populate a table with an INSERT statement • Remaining slides: Populate a table using the grid view - annotated • Slide 5: Access the grid and enter data • Slide 6: MySQL generates INSERT code • Slide 7: Finalize the insert process • Slide 8: View and understand the result • Feedback? Please email feedback to [email protected] New SQL Open and SQL Save SQL Execute SQL Execute SQL script Create Initial FILE button FILE button FILE button script button under cursor button Dababase and a Single Table As soon as you create a new Code to create a database database or a new table, the and a table in the database in schemas window is updated. a new SQL script file. You may need to use the refresh Note the following: before it becomes visible. • Can create a DB only once • The USE temp statement that sets temp as the current database • Can create a table only once • The text in grey are comments. Ignored by SQL, but important to us In this window you find feedback • For creating the first on your code: if it worked, or if database and tables, there was an error. The share please use the SQL create table creation was successful. table statement Populate a Table with Data Using INSERT Code to populate a table with INSERT statement. Note the following: • This statement creates a single record/tuple in the table. • You need such an INSERT statement for each record you need in the table. • If you try to insert a record with a duplicate primary key, if gives an error. Error generated when attempting to insert a record with a duplicate primary key. Enter Records with Grid Data Entry • Steps: 1. Hover over the table (in this case share), and click on table grid next to the table name. The grid view opens. 2. Click on the null cell in the left-most column to start data entry. 3. You can enter as many rows as you want. 4. NOTE: IMPORTANT: typing records in the grid does NOT automatically save the data to the table: extra steps are required (next slides) Start data entry Table grid button Populate Table with Data in Grid Data entered in the grid, an • Steps: example 1. Four new records were entered in the grid. 2. To save those data to the share table, click the Apply button on the bottom right of the grid. 3. In the next pop-up window, you will see the SQL INSERT code generated for the data you typed in the grid. Click the Apply button to save the data to the share table. 4. MySQL executes the code, and your data are now in the table (next slide) Click the Apply button to execute the generated SQL codes Finalize It • Steps 1. In the next pop-up window, finalize the execution of the SQL statements: click Finish 2. MySQL will automatically generate a SELECT statement in a new tab to show all the data in the table. 3. You can execute the statement and verify all your tuples are present. 4. You can repeat the process as often as needed to add more data as needed Click the Finish button to complete the process. Check the Results … Check out the generated SQL SELECT code, in a new tab Check out the new data in the results grid Check out the feedback on execution: 5 rows returned Now you are ready to do a lot of things: • Add more data • Write new SELECT queries, following the examples in your book or creating your own • Save your own SELECT queries in an SQL file and save it. • Add your name and notes on what queries do as comments.
Recommended publications
  • Keys Are, As Their Name Suggests, a Key Part of a Relational Database
    The key is defined as the column or attribute of the database table. For example if a table has id, name and address as the column names then each one is known as the key for that table. We can also say that the table has 3 keys as id, name and address. The keys are also used to identify each record in the database table . Primary Key:- • Every database table should have one or more columns designated as the primary key . The value this key holds should be unique for each record in the database. For example, assume we have a table called Employees (SSN- social security No) that contains personnel information for every employee in our firm. We’ need to select an appropriate primary key that would uniquely identify each employee. Primary Key • The primary key must contain unique values, must never be null and uniquely identify each record in the table. • As an example, a student id might be a primary key in a student table, a department code in a table of all departments in an organisation. Unique Key • The UNIQUE constraint uniquely identifies each record in a database table. • Allows Null value. But only one Null value. • A table can have more than one UNIQUE Key Column[s] • A table can have multiple unique keys Differences between Primary Key and Unique Key: • Primary Key 1. A primary key cannot allow null (a primary key cannot be defined on columns that allow nulls). 2. Each table can have only one primary key. • Unique Key 1. A unique key can allow null (a unique key can be defined on columns that allow nulls.) 2.
    [Show full text]
  • Staroffice 6.0 Software Setting up Database Connections
    StarOffice™ 6.0 Software Setting Up Database Connections Sun Microsystems, Inc. 901 San Antonio Road Palo Alto, CA 94303 U.S.A. 650-960-1300 Part No. 817-0364-05 September 2002, Revision A Copyrights and Trademarks Copyright © 2002 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries. This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this document may be repro- duced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. This product is based in part on the work of the Independent JPEG Group, The FreeType Project and the Catharon Typography Project. Portions Copyright 2000 SuSE, Inc. Word for Word Copyright © 1996 Inso Corp. International CorrectSpell spelling correction system Copyright © 1995 by Lernout & Hauspie Speech Products N.V. All rights reserved. Source code for portions of this product are available under the Mozilla Public License at the following sites: http://www.mozilla.org/, http://www.jclark.com/, and http://www.gingerall.com.
    [Show full text]
  • Data Definition Language
    1 Structured Query Language SQL, or Structured Query Language is the most popular declarative language used to work with Relational Databases. Originally developed at IBM, it has been subsequently standard- ized by various standards bodies (ANSI, ISO), and extended by various corporations adding their own features (T-SQL, PL/SQL, etc.). There are two primary parts to SQL: The DDL and DML (& DCL). 2 DDL - Data Definition Language DDL is a standard subset of SQL that is used to define tables (database structure), and other metadata related things. The few basic commands include: CREATE DATABASE, CREATE TABLE, DROP TABLE, and ALTER TABLE. There are many other statements, but those are the ones most commonly used. 2.1 CREATE DATABASE Many database servers allow for the presence of many databases1. In order to create a database, a relatively standard command ‘CREATE DATABASE’ is used. The general format of the command is: CREATE DATABASE <database-name> ; The name can be pretty much anything; usually it shouldn’t have spaces (or those spaces have to be properly escaped). Some databases allow hyphens, and/or underscores in the name. The name is usually limited in size (some databases limit the name to 8 characters, others to 32—in other words, it depends on what database you use). 2.2 DROP DATABASE Just like there is a ‘create database’ there is also a ‘drop database’, which simply removes the database. Note that it doesn’t ask you for confirmation, and once you remove a database, it is gone forever2. DROP DATABASE <database-name> ; 2.3 CREATE TABLE Probably the most common DDL statement is ‘CREATE TABLE’.
    [Show full text]
  • Mysql Query Browser Mysql Query Browser This Is a Translation of the Mysql Query Browser Manual That Can Be Found at Dev.Mysql.Com
    MySQL Query Browser MySQL Query Browser This is a translation of the MySQL Query Browser Manual that can be found at dev.mysql.com. The original MySQL Query Browser Manual is in English, and this translation is not necessarily as up to date as the English version. Esta es una traduccion del manual de MySQL Query Browser el cual puede ser encontrado en dev.mysql.com. El Manual original de MySQL Query Browser se encuentra en Inglés, y esta traduccion no necesariamente es tan actualizada como la versión en Inglés. Edwin Cruz <ecruz @ medel.com.mx> ha traducido este manual del Inglés. El es gerente de sistemas y vive en Aguascalientes, México. Edwin cumplió su educación en 2005 con grado de ingenieria en ciencias de la computa- ción. Como desarrollador, Edwin ha estado trabajando con LAMP Stack por tres años. Antes de obtener su empleo actual, en una compañia de transporte, Edwin trabajo en Texas Instruments Mexico. Resumen Este es el Manual de MySQL Query Browser Documento generado en: 2010-03-14 (revision: 542) Copyright © 1997-2007 MySQL AB, 2008-2010 Sun Microsystems, Inc. All rights reserved. U.S. Government Rights - Commercial software. Govern- ment users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Use is sub- ject to license terms. Sun, Sun Microsystems, the Sun logo, Java, Solaris, StarOffice, MySQL Enterprise Monitor 2.0, MySQL logo™ and MySQL™ are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. UNIX is a registered trademark in the U.S.
    [Show full text]
  • Chapter 8 Getting Started with Base
    Getting Started Guide Chapter 8 Getting Started with Base OpenOffice.org’s Database Component Copyright This document is Copyright © 2008 by its contributors as listed in the section titled Authors. You may distribute it and/or modify it under the terms of either the GNU General Public License, version 3 or later, or the Creative Commons Attribution License, version 3.0 or later. All trademarks within this guide belong to their legitimate owners. Authors Dan Lewis Iain Roberts Magnus Adielsson Jean Hollis Weber Feedback Maintainer: Dan Lewis Please direct any comments or suggestions about this document to: [email protected] Acknowledgments As the maintainer of this document, I would like to personally thank the other authors of it. Without them, this document would not have the quality it does. Neither would it contain as much information. Iain Roberts and Magnus Adielsson offered many sound suggestions on content as well as format. Jean Hollis Weber with many years of technical writing experience has suggested many changes which have made this document much more understandable. Special thanks also go to those who have translated this document into other languages so that non-English speaking people have access to this information. Publication date and software version Published 13 October 2008. Based on OpenOffice.org 3.0. You can download an editable version of this document from http://oooauthors.org/en/authors/userguide3/published/ Contents Copyright...............................................................................................2
    [Show full text]
  • Oracle/Sun Microsystems: the Challenge of Reviewing a Merger Involving Open Source Software
    Mergers Oracle/Sun Microsystems: The challenge of reviewing a merger involving open source software Carl-Christian Buhr, Sabine Crome, Adrian Lübbert, Vera Pozzato, Yvonne Simon, Robert Thomas (1) 1. Introduction (1) 2. Oracle, Sun and the IT stack On 21 January 2010 the Commission uncondition- The US company Oracle is a major business soft- ally cleared the planned takeover of Sun Microsys- ware vendor. It develops and distributes enterprise tems (‘Sun’), a software and hardware vendor, by software solutions and related services, including Oracle Corporation (‘Oracle’), one of the world’s middleware, databases and enterprise application leading software companies. The clearance followed software. Sun is active in hardware (servers, desk- an extensive investigation into the database market tops, microelectronics, and storage devices) and where Oracle was the leading proprietary vendor software, including operating systems, Java software and Sun the leading open source vendor. The case development technology, middleware, database soft- also attracted a certain level of public attention and ware and related services. triggered reactions by many parties. The legal test The product offerings of Oracle and Sun can be applied in this case was not based on the acquisi- seen as part of an IT or technology ‘stack’ which tion or strengthening of a dominant position but consists of the various hardware and software on the elimination of an important competitive components necessary for companies to ultimate- force, which would be Sun’s MySQL. The Horizon- ly use business software applications. Hardware tal Merger Guidelines (2) recognize that some firms, products, including servers, storage units and despite having a relatively small market share may client PCs, constitute the first layer.
    [Show full text]
  • KB SQL Database Administrator Guide a Guide for the Database Administrator of KB SQL
    KB_SQL Database Administrator Guide A Guide for the Database Administrator of KB_SQL © 1988-2019 by Knowledge Based Systems, Inc. All rights reserved. Printed in the United States of America. No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from KB Systems, Inc., as governed by United States and international copyright laws. The information contained in this document is subject to change without notice. KB Systems, Inc., does not warrant that this document is free of errors. If you find any problems in the documentation, please report them to us in writing. Knowledge Based Systems, Inc. 43053 Midvale Court Ashburn, Virginia 20147 KB_SQL is a registered trademark of Knowledge Based Systems, Inc. MUMPS is a registered trademark of the Massachusetts General Hospital. All other trademarks or registered trademarks are properties of their respective companies. Table of Contents Preface ................................................. vii Purpose ............................................. vii Audience ............................................ vii Conventions Used in this Manual ...................................................................... viii The Organization of this Manual ......................... ... x Additional Documentation .............................. xii Chapter 1: An Overview of the KB_SQL User Groups and Menus ............................................................................................................
    [Show full text]
  • Oracle® Virtual Desktop Infrastructure Update Guide for Version 3.2.2
    Oracle® Virtual Desktop Infrastructure Update Guide for Version 3.2.2 April 2011 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
    [Show full text]
  • Database Models
    Enterprise Architect User Guide Series Database Models The Sparx Systems Enterprise Architect Database Builder helps visualize, analyze and design system data at conceptual, logical and physical levels, generate database objects from a model using customizable Transformations, and reverse engineer a DBMS. Author: Sparx Systems Date: 16/01/2019 Version: 1.0 CREATED WITH Table of Contents Database Models 4 Data Modeling Overview 5 Conceptual Data Model 7 Logical Data Model 8 Entity Relationship Diagrams (ERDs) 9 Physical Data Models 13 Database Modeling 15 Create a Data Model from a Model Pattern 16 Create a Data Model Diagram 18 Example Data Model Diagram 20 The Database Builder 22 Opening the Database Builder 24 Working in the Database Builder 26 Columns 30 Create Database Table Columns 31 Delete Database Table Columns 33 Reorder Database Table Columns 34 Constraints/Indexes 35 Database Table Constraints/Indexes 36 Primary Keys 39 Database Indexes 42 Unique Constraints 45 Foreign Keys 46 Check Constraints 50 Table Triggers 52 SQL Scratch Pad 54 Database Compare 56 Execute DDL 62 Database Objects 65 Database Tables 66 Create a Database Table 68 Database Table Columns 70 Create Database Table Columns 71 Delete Database Table Columns 73 Reorder Database Table Columns 74 Working with Database Table Properties 75 Set the Database Type 76 Set Database Table Owner/Schema 77 Set MySQL Options 78 Set Oracle Database Table Properties 79 Database Table Constraints/Indexes 80 Primary Keys 83 Non Clustered Primary Keys 86 Database Indexes 87 Unique
    [Show full text]
  • Ms Sql Server Alter Table Modify Column
    Ms Sql Server Alter Table Modify Column Grinningly unlimited, Wit cross-examine inaptitude and posts aesces. Unfeigning Jule erode good. Is Jody cozy when Gordan unbarricade obsequiously? Table alter column, tables and modifies a modified column to add a column even less space. The entity_type can be Object, given or XML Schema Collection. You can use the ALTER statement to create a primary key. Altering a delay from Null to Not Null in SQL Server Chartio. Opening consent management ebook and. Modifies a table definition by altering, adding, or dropping columns and constraints. RESTRICT returns a warning about existing foreign key references and does not recall the. In ms sql? ALTER to ALTER COLUMN failed because part or more. See a table alter table using page free cloud data tables with simple but block users are modifying an. SQL Server 2016 introduces an interesting T-SQL enhancement to improve. Search in all products. Use kitchen table select add another key with cascade delete for debate than if column. Columns can be altered in place using alter column statement. SQL and the resulting required changes to make via the Mapper. DROP TABLE Employees; This query will remove the whole table Employees from the database. Specifies the retention and policy for lock table. The default is OFF. It can be an integer, character string, monetary, date and time, and so on. The keyword COLUMN is required. The table is moved to the new location. If there an any violation between the constraint and the total action, your action is aborted. Log in ms sql server alter table to allow null in other sql server, table statement that can drop is.
    [Show full text]
  • 3 Data Definition Language (DDL)
    Database Foundations 6-3 Data Definition Language (DDL) Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Roadmap You are here Data Transaction Introduction to Structured Data Definition Manipulation Control Oracle Query Language Language Language (TCL) Application Language (DDL) (DML) Express (SQL) Restricting Sorting Data Joining Tables Retrieving Data Using Using ORDER Using JOIN Data Using WHERE BY SELECT DFo 6-3 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. 3 Data Definition Language (DDL) Objectives This lesson covers the following objectives: • Identify the steps needed to create database tables • Describe the purpose of the data definition language (DDL) • List the DDL operations needed to build and maintain a database's tables DFo 6-3 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. 4 Data Definition Language (DDL) Database Objects Object Description Table Is the basic unit of storage; consists of rows View Logically represents subsets of data from one or more tables Sequence Generates numeric values Index Improves the performance of some queries Synonym Gives an alternative name to an object DFo 6-3 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. 5 Data Definition Language (DDL) Naming Rules for Tables and Columns Table names and column names must: • Begin with a letter • Be 1–30 characters long • Contain only A–Z, a–z, 0–9, _, $, and # • Not duplicate the name of another object owned by the same user • Not be an Oracle server–reserved word DFo 6-3 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. 6 Data Definition Language (DDL) CREATE TABLE Statement • To issue a CREATE TABLE statement, you must have: – The CREATE TABLE privilege – A storage area CREATE TABLE [schema.]table (column datatype [DEFAULT expr][, ...]); • Specify in the statement: – Table name – Column name, column data type, column size – Integrity constraints (optional) – Default values (optional) DFo 6-3 Copyright © 2015, Oracle and/or its affiliates.
    [Show full text]
  • Relational Database Fundamentals
    05_04652x ch01.qxp 7/10/06 1:45 PM Page 7 Chapter 1 Relational Database Fundamentals In This Chapter ᮣ Organizing information ᮣ Defining database ᮣ Defining DBMS ᮣ Comparing database models ᮣ Defining relational database ᮣ Considering the challenges of database design QL (pronounced ess-que-ell, not see’qwl) is an industry-standard language Sspecifically designed to enable people to create databases, add new data to databases, maintain the data, and retrieve selected parts of the data. Various kinds of databases exist, each adhering to a different conceptual model. SQL was originally developed to operate on data in databases that follow the relational model. Recently, the international SQL standard has incorporated part of the object model, resulting in hybrid structures called object-relational databases. In this chapter, I discuss data storage, devote a section to how the relational model compares with other major models, and provide a look at the important features of relational databases. Before I talk about SQL, however, I need to nail down what I mean by the term database. Its meaning has changed as computers have changed the way people record and maintain information. COPYRIGHTED MATERIAL Keeping Track of Things Today, people use computers to perform many tasks formerly done with other tools. Computers have replaced typewriters for creating and modifying documents. They’ve surpassed electromechanical calculators as the best way to do math. They’ve also replaced millions of pieces of paper, file folders, and file cabinets as the principal storage medium for important information. Compared to those old tools, of course, computers do much more, much faster — and with greater accuracy.
    [Show full text]