DOCSLIB.ORG

SQL Developer Data Modeler: a Top-Down Product Overview

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SQL Developer Data Modeler: a Top-Down Product Overview SQL Developer Data Modeler: A Top-Down Product Overview Sue Harper Oracle United Kingdom Keywords: SQL Developer Data Modeler, ERD, DDL Generation, model, capture, design Introduction Oracle SQL Developer Data Modeler is a graphical data modeling tool for creating, browsing and editing data models, including logical, relational, physical, multi-dimensional, and data type models. It supports forward and reverse engineering from Oracle Database, Microsoft SQL Server and IBM DB2 databases and the generation of DDL scripts for these databases. SQL Developer Data Modeler offers features and utilities that enhance the data modeling experience, improve productivity and promote the use of standards. SQL Developer Data Modeler is designed for a broad spectrum of database developers; from business architects to DBAs and from database to application developers, serving as a powerful communication tool between developers and business users. In this article we review the main modelers and features in SQL Developer Data Modeler 2.0 starting with the logical model and progressing through the features to the final DDL script. Often called the top-down approach, this is not the only flow of work through the product, as indeed, users can start by importing a data model and reverse engineering the objects to create an initial diagram and progressing from there. We will refer to various methods of creating models and updating the database using the product. Integrated Models SQL Developer Data Modeler provides facilities to build sets of related and integrated models. Many consider the core of SQL Developer Data Modeler to be the logical model. It is this logical model that provides a true implementation-independent view of enterprise information. Using the logical model, often referred to as the Entity Relational Model (ERD), you can engineer relational models or multidimensional models. The ERD is also ultimately the source of many different physical implementations. A logical model or a part of it (subject area or sub view), can be transformed to one or more relational models. Each relational model can have an unlimited number of physical implementations in the form of physical models (referred to as RDBMS Sites in SQL Developer Data Modeler), with each physical model based on a supported database. Logical Models The logical model (or ERD) in SQL Developer Data Modeler includes standard logical modeling facilities, such as drawing entities and relationships. It also supports the choice of Barker or Bachman notations. The diagram itself provides for box-in-box representation for the display of the super-type and sub-type hierarchy of entities and you can easily create and display arcs, for the support of exclusive relationships. The image below provides an example of a logical model using the Barker notation and the box-in-box representation of super-types and sub-types. Figure 1: SQL Developer Data Modeler Logical Model Relational Models The SQL Developer Data Modeler relational model is an intermediate model between the logical model and the physical models. Some refer to this as the server diagram or data model as it is made up of tables, columns and constraints and is a result of the transformation from the logical model. The relational model supports relational design decisions independent of the constraints of the target physical platform(s), which means that you can use one design for any of the supported target databases. All many-to-many relationships and all super-type/sub-types entity hierarchies are resolved during forward engineering (transformation) of the logical model to a relational model. You can apply naming standardization to the models during the transformation, by applying a glossary of terms. Physical Models It is the physical model that allows you to add implementation-specific detail. Here you add structure and definition to the objects, such as adding partitions and sub-partition detail, or adding elements not exposed on a diagram, such as sequences, tablespaces and roles. There is no diagram associated with the physical model, so all changes and updates are through the property dialogs which you can invoke from the browser. Data Type and Structured Type Models The Data Types model is independent of each of the above models, allowing you to create and visualize structured types and the inheritance hierarchies of structured types, defining distinct and collection (array) types on a model and then use these in either the logical or relational models. You can also add physical detail to these data types through the physical model. Creating New Models On opening SQL Developer Data Modeler, two empty model tabs, the logical and relational models, are automatically opened. To start creating a new model, use the toolbar and click on the appropriate button, for example the entity or table button, and then click on the model. Each action invokes the associated dialog, allowing you to create or update the elements on the diagram. Once you have created the logical model you can forward engineer this to a relational model. The Data Modeler also supports the reverse process. Importing Existing Models You can also import existing logical models, multi-dimensional, or relational models instead of creating them from scratch. You can create relational models by importing script files (DDL) or by importing directly from the data dictionary. SQL Developer Data Modeler can also import directly from the Oracle Designer repository or import CA ERwin Data Modeler export files. Extensive and wizard-led engineering capabilities allow you to re-engineer a relational model to a logical model or to engineer a logical model to one or more relational models, where both models can be kept synchronized. Importing from the Data Dictionary While not necessarily a part of the top-down approach, you can also create models by importing or reverse engineering directly from the database. SQL Developer Data Modeler provides selection lists for all supported objects and with it the ability to filter out secondary tables. While importing, you can import the objects from one or more schemas. The Data Modeler creates a single diagram for all tables and views and a separate subview for each schema imported. Generating Scripts Once you have created the models and updated the physical properties for the objects, you can generate the DDL scripts. SQL Developer Data Modeler supports generation of DDL scripts for Oracle, DB2 and SQL Server. The DDL generation supports a wide variety of features, by allowing you to generate interactive DDL scripts, add additional code into the scripts, and even name substitution facilities to ease database migration tasks. For example, you can have the same set of database objects exist in different databases (test, development, production environments, etc.) but with different naming templates. Updating the Database through DDL Scripts Once you have established your data model and have generated and executed the DDL, you may also want to update the database using the Data Modeler. SQL Developer Data Modeler enables safe and effective through the generated DDL scripts. To update an existing database design, you need to determine whether it is the database or the model which is to be the “point of truth”. By this we mean that you might want to use the database to update your model. This is easily done by importing the objects in the database to the same data model and allowing the tool to update the diagram. A Compare Model dialog allows you do select the objects you want updated. If, on the other hand, you want the model to update the database, you need to create the alter database DDL scripts. This is also achieved through the import menu, by directing the import to “Swap Target Model”. In the following image, the model, with details listed on the left, includes the CATEGORIES table, which does not appear in the selected data dictionary schema import, displayed on the right. In addition, the process reveals that there are additional tables, such as the EMP and DEPT tables, in the schema selection, which are not on the model. In both cases, the user has the choice of including the objects in the DDL. The review and save the DDL that updates the database, click “DDL Preview”. Figure 2: SQL Developer Data Modeler: Compare Model Dialog Formatting, Sub views and Displays The easiest way of managing a large set of objects is to split the model into subject areas. SQL Developer Data Modeler refers to these subject areas as subviews. Typically, a subview is a group of related objects on a diagram and any changes you make to the object in the subview are reflected in the main model. On importing multiple schemas, a single relational model is created for all the objects and a separate subview is automatically created per database. Subviews make it easier to maintain larger models. You can also control colors, fonts and the dimensions of the objects on a model. Diagram Linking In addition to standard diagram drawing capabilities, SQL Developer Data Modeler supports diagram nesting or linking. For example, a data flow diagram can be visually nested in a relational. Nested diagrams can be visualized as icons or in a composite view. If a nested diagram has more than one display, one of them can be selected to represent the diagram. Naming Standards SQL Developer Data Modeler supports naming standard glossaries, and also provides flexible and unrestricted naming rules through naming templates. These template or name patterns mean that you can define naming rules for table elements. You can create name patterns for indexes and constraints (including Primary Key and Unique key) using a combination of predefined variables, e.g. {table}, {child}, {parent}, {column}, {seq_nr}, {model} and alphanumeric constants and combining these, optionally with the SUBSTR function to restrict the total length of the word.
Load more

Recommended publications
  • Powerdesigner 16.6 Data Modeling
    SAP® PowerDesigner® Document Version: 16.6 – 2016-02-22 Data Modeling Content 1 Building Data Models ...........................................................8 1.1 Getting Started with Data Modeling...................................................8 Conceptual Data Models........................................................8 Logical Data Models...........................................................9 Physical Data Models..........................................................9 Creating a Data Model.........................................................10 Customizing your Modeling Environment........................................... 15 1.2 Conceptual and Logical Diagrams...................................................26 Supported CDM/LDM Notations.................................................27 Conceptual Diagrams.........................................................31 Logical Diagrams............................................................43 Data Items (CDM)............................................................47 Entities (CDM/LDM)..........................................................49 Attributes (CDM/LDM)........................................................55 Identifiers (CDM/LDM)........................................................58 Relationships (CDM/LDM)..................................................... 59 Associations and Association Links (CDM)..........................................70 Inheritances (CDM/LDM)......................................................77 1.3 Physical Diagrams..............................................................82
    [Show full text]
  • Data Modeler User's Guide
    Oracle® SQL Developer Data Modeler User's Guide Release 18.1 E94838-01 March 2018 Oracle SQL Developer Data Modeler User's Guide, Release 18.1 E94838-01 Copyright © 2008, 2018, Oracle and/or its affiliates. All rights reserved. Primary Author: Celin Cherian Contributing Authors: Chuck Murray Contributors: Philip Stoyanov 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 is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Relational and Object-Oriented Databases
    Relational and Object-Oriented Databases by Willi-Hans Steeb International School for Scientific Computing Contents 1 What is a table? 1 1.1 Introduction . 1 1.2 Examples . 5 1.3 Tables in Programs . 8 1.4 Table and Relation . 33 2 Structured Query Language 35 2.1 Introduction . 35 2.2 Integrity Rules . 38 2.3 SQL Commands . 39 2.3.1 Introduction . 39 2.3.2 Aggregate Function . 40 2.3.3 Arithmetic Operators . 40 2.3.4 Logical Operators . 40 2.3.5 SELECT Statement . 41 2.3.6 INSERT Command . 45 2.3.7 DELETE Command . 46 2.3.8 UPDATE Command . 47 2.3.9 CREATE TABLE Command . 48 2.3.10 DROP TABLE Command . 51 2.3.11 ALTER TABLE Command . 52 2.4 Set Operators . 53 2.5 Views . 60 2.6 Primary and Foreign Keys . 62 2.7 Datatypes in SQL . 63 2.8 Joins . 66 2.9 Stored Procedure . 71 2.10 MySQL Commands . 72 2.11 Cursors . 73 2.12 PL and SQL . 75 2.13 ABAP/4 and SQL . 76 2.14 Query Processing and Optimization . 77 i 3 Normal Forms 83 3.1 Introduction . 83 3.2 Anomalies . 87 3.3 Example . 89 3.4 Fourth and Fifth Normal Forms . 93 4 Transaction 101 4.1 Introduction . 101 4.2 Data Replication . 107 4.3 Locks . 108 4.4 Deadlocking . 111 4.5 Threads . 117 4.5.1 Introduction . 117 4.5.2 Thread Class . 119 4.5.3 Example . 121 4.5.4 Priorities . 123 4.5.5 Synchronization and Locks .
    [Show full text]
  • An Introduction to Oracle SQL Developer Data Modeler
    An Oracle White Paper June 2009 An Introduction to Oracle SQL Developer Data Modeler Oracle White Paper— An Introduction to Oracle SQL Developer Data Modeler Introduction ....................................................................................... 1 Oracle SQL Developer Data Modeler ................................................ 2 Architecture ................................................................................... 2 Integrated Models.............................................................................. 4 Logical Models .............................................................................. 4 Relational Models.......................................................................... 5 Physical Models............................................................................. 5 Multi-dimensional Models .............................................................. 7 Data Type and Structured Type Models ...................................... 10 Spatial Models............................................................................. 11 Creating Models .............................................................................. 13 Creating New Models .................................................................. 13 Importing from the Data Dictionary .............................................. 13 Importing from Oracle Designer................................................... 14 Generating Scripts........................................................................... 15 Generating DDL
    [Show full text]
  • Handling Unstructured Data Type in DB2 and Oracle
    Communications of the IIMA Volume 3 Issue 2 Article 6 2003 Handling Unstructured Data Type in DB2 and Oracle Alexander P. Pons Computer Information Systems, University of Miami Hassan Aljifri Computer Information Systems, University of Miami Follow this and additional works at: https://scholarworks.lib.csusb.edu/ciima Recommended Citation Pons, Alexander P. and Aljifri, Hassan (2003) "Handling Unstructured Data Type in DB2 and Oracle," Communications of the IIMA: Vol. 3 : Iss. 2 , Article 6. Available at: https://scholarworks.lib.csusb.edu/ciima/vol3/iss2/6 This Article is brought to you for free and open access by CSUSB ScholarWorks. It has been accepted for inclusion in Communications of the IIMA by an authorized editor of CSUSB ScholarWorks. For more information, please contact [email protected]. Alexander P. Pons, Hassan Aljifri Handling Unstructured Data Type in DB2 and Oracle Alexander P. Pons Computer Information Systems, University of Miami, 421 Jenkins Building, Coral Gables, FL 33146 Phone: 305-284-1960, Fax: 305-284-5161, [email protected] Hassan Aljifri Computer Information Systems, University of Miami, 421 Jenkins Building, Coral Gables, FL 33146 Phone: 305-284-4767, Fax: 305-284-5161, [email protected] ABSTRACT The objective of our work is to determine which mainstream object-relational database management systems (ORDMS) provide convenient facilities for the storage and manipulation of unstructured data objects. These objects, which consist of video, audio, photographs, and even executable code such as Java applets, are becoming readily employed by desktop, network, and Internet applications. Typically, these ORDMSs must store the objects in a manner by which they can be easily accessed, but more importantly, easily processed during either storage or retrieval.
    [Show full text]
  • Oracle® SQL Developer Data Modeler User's Guide
    Oracle® SQL Developer Data Modeler User's Guide Release 17.3 E90546-01 September 2017 Oracle SQL Developer Data Modeler User's Guide, Release 17.3 E90546-01 Copyright © 2008, 2017, Oracle and/or its affiliates. All rights reserved. Primary Author: Celin Cherian Contributing Authors: Chuck Murray Contributors: Philip Stoyanov 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 is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • 25 Object-Database Systems
    25 OBJECT-DATABASESYSTEMS with Joseph M. Hellerstein U. C. Berkeley You know my methods, Watson. Apply them. —Arthur Conan Doyle, The Memoirs of Sherlock Holmes Relational database systems support a small, fixed collection of data types (e.g., in- tegers, dates, strings), which has proven adequate for traditional application domains such as administrative data processing. In many application domains, however, much more complex kinds of data must be handled. Typically this complex data has been stored in OS file systems or specialized data structures, rather than in a DBMS. Ex- amples of domains with complex data include computer-aided design and modeling (CAD/CAM), multimedia repositories, and document management. As the amount of data grows, the many features offered by a DBMS—for example, reduced application development time, concurrency control and recovery, indexing support, and query capabilities—become increasingly attractive and, ultimately, nec- essary. In order to support such applications, a DBMS must support complex data types. Object-oriented concepts have strongly influenced efforts to enhance database support for complex data and have led to the development of object-database systems, which we discuss in this chapter. Object-database systems have developed along two distinct paths: Object-oriented database systems: Object-oriented database systems are proposed as an alternative to relational systems and are aimed at application domains where complex objects play a central role. The approach is heavily in- fluenced by object-oriented programming languages and can be understood as an attempt to add DBMS functionality to a programming language environment. Object-relational database systems: Object-relational database systems can be thought of as an attempt to extend relational database systems with the func- tionality necessary to support a broader class of applications and, in many ways, provide a bridge between the relational and object-oriented paradigms.
    [Show full text]
  • Oracle to DB2 Conversion Guide: Compatibility Made Easy
    Front cover IBM® Information Management Software Oracle to DB2 Conversion Guide: Compatibility Made Easy Move Oracle to DB2 efficiently and effectively Learn about DB2 10.5 Oracle Database compatibility features Use Oracle PL/SQL skills directly with DB2 10.5 Yvonne Chan Nick Ivanov Olaf Mueller ibm.com/redbooks International Technical Support Organization Oracle to DB2 Conversion Guide: Compatibility Made Easy September 2013 SG24-7736-02 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. Third Edition (September 2013) This edition applies to IBM DB2 for Linux, UNIX, and Windows Version 10.5. © Copyright International Business Machines Corporation 2009, 2013. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . x Preface . xi Authors . xii Acknowledgements . xiii Now you can become a published author, too! . xiv Comments welcome. xiv Stay connected to IBM Redbooks publications . xv Summary of changes . xvii September 2013, Third Edition. xvii Chapter 1. Introduction. 1 1.1 DB2 family of products . 2 1.1.1 DB2 editions . 2 1.1.2 IBM DB2 10.5 Advanced Enterprise Edition features . 6 1.1.3 DB2 10 autonomic computing features . 7 1.1.4 Introduction to PureData . 9 1.2 DB2 Oracle database compatibility features overview . 9 1.2.1 Concurrency control . 10 1.2.2 Data types . 11 1.2.3 Implicit casting. 11 1.2.4 SQL Standard . 12 1.2.5 PL/SQL . 12 1.2.6 Built-in packages.
    [Show full text]
  • ISG STAFF WORKING PAPERS Objects in the Database
    soG ISG STAFF WORKING PAPERS Public Disclosure Authorized Public Disclosure Authorized Public Disclosure Authorized Objects in the Database: A Reality Check Parvez Bashir Information Public Disclosure Authorized Officer, ISGEC IFl - I Sol Grion ISG STAFF WORKING PAPERS ISG Staff Working Papers are reviewed by the VP-CIO and by the ISG Senior Management Team. Papers are evaluated and the best of the papers will be recognized. The series is envisioned to be forward-looking and cover a broad range of topics. Over a period of time, the papers will be compiled and published as a book. ffMy= .I Parvez Bashir Information Officer, ISGEC Objects in the Database: A Reality Check The RDBMS (Relational Database Management System) ruled the database roost in the 1980s and 00 (Object Oriented) programming languages revolutionized software development in the 1990s. RDBMSs and 00 programming languages have complementary strengths. Relational database systems are good for managing large amounts of data; object oriented programming languages are good at expressing complex relationships among objects. Relational database systems are good for data retrieval but provide little support for data manipulation; object oriented programming languages are excellent at data manipulation but provide little or no support for data persistence and retrieval. These complementary strengths have given birth to a new breed of database management systems popularly known as Object Relational Database Management Systems (ORDBMS). The other database model which deals purely with objects is the ODBMS (Object Database Management System). ODBMSs pre-date the object relational model and have been in use since time immemorial in niche applications including multimedia.
    [Show full text]
  • Programming Server Applications
    IBM® DB2 Universal Database™ Application Development Guide: Programming Server Applications Ve r s i o n 8 SC09-4827-00 IBM® DB2 Universal Database™ Application Development Guide: Programming Server Applications Ve r s i o n 8 SC09-4827-00 Before using this information and the product it supports, be sure to read the general information under Notices. This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such. You can order IBM publications online or through your local IBM representative. v To order publications online, go to the IBM Publications Center at www.ibm.com/shop/publications/order v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at www.ibm.com/planetwide To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU (426-4968). When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1993 - 2002. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About This Book ..........vii Chapter 3. SQL-Bodied Routines ....59 CREATE Statements for SQL-Bodied Routines 59 Part 1. Routines (Stored Dynamic SQL in SQL-Bodied Routines .
    [Show full text]
  • Oracle® SQL Developer Data Modeler User's Guide
    Oracle® SQL Developer Data Modeler User's Guide Release 17.4 E92382-01 December 2017 Oracle SQL Developer Data Modeler User's Guide, Release 17.4 E92382-01 Copyright © 2008, 2017, Oracle and/or its affiliates. All rights reserved. Primary Author: Celin Cherian Contributing Authors: Chuck Murray Contributors: Philip Stoyanov 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 is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Data Movement Utilities Guide and Reference
    IBM® DB2 Universal Database™ Data Movement Utilities Guide and Reference Ve r s i o n 8 SC09-4830-00 IBM® DB2 Universal Database™ Data Movement Utilities Guide and Reference Ve r s i o n 8 SC09-4830-00 Before using this information and the product it supports, be sure to read the general information under Notices. This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such. You can order IBM publications online or through your local IBM representative. v To order publications online, go to the IBM Publications Center at www.ibm.com/shop/publications/order v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at www.ibm.com/planetwide To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU (426-4968). When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1999, 2002. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About This Book ..........vii Parallelism and Loading .......110 Who Should Use this Book .......vii Privileges, Authorities, and Authorizations How this Book is Structured ......vii Required to Use Load ........111 Using Load ............112 Chapter 1.
    [Show full text]