DOCSLIB.ORG

Multi-Schema-Version Data Management

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Multi-Schema-Version Data Management Multi-Schema-Version Data Management Dissertation submitted August 31, 2017 by Dipl.-Inf. Kai Herrmann born July 25, 1988 in Dresden at Technische Universität Dresden and Aalborg Universitet Supervisors: Prof. Dr.-Ing. Wolfgang Lehner Prof. Torben Bach Pedersen ,7%, R o SI ' & JOINT PH.D. DEGREE The thesis is jointly submitted to the Faculty of Computer Science at Technische Universität Dresden (TUD) and the Technical Faculty of IT and Design at Aalborg University (AAU), in partial fulfillment of the requirements within the scope of the IT4BIDC program for the joint Ph.D. degree in computer science (TUD: Dr.-Ing., AAU: Ph.D. in computer science). The thesis is not submitted to any other organization at the same time. DEFENDED: DECEMBER 13, 2017 IN DRESDEN PH.D. COMMITTEES: TUD Ph.D. Supervisor: Prof. Dr.-Ing. Wolfgang Lehner Technische Universität Dresden, Dresden, Germany AAU Ph.D. Supervisor: Prof. Torben Bach Pedersen Aalborg University, Aalborg, Denmark TUD Ph.D. Committee: Prof. Dr. Franz Baader Technische Universität Dresden, Dresden, Germany Prof. Dr.-Ing. Wolfgang Lehner Technische Universität Dresden, Dresden, Germany Prof. Dr.-Ing. Stefan Deßloch Technische Universität Kaiserslautern, Kaiserslautern, Germany Prof. Dr. Thorsten Strufe Technische Universität Dresden, Dresden, Germany Prof. Torben Bach Pedersen Aalborg University, Aalborg, Denmark AAU Ph.D. Committee: Prof. Torben Bach Pedersen Aalborg University, Aalborg, Denmark Prof. Dr.-Ing. Stefan Deßloch Technische Universität Kaiserslautern, Kaiserslautern, Germany Panos Vassiliadis, Associate Professor University of Ioannina, Ioannina, Greece Kristian Torp, Associate Professor Aalborg University, Aalborg, Denmark © Copyright by Kai Herrmann. The author has obtained the rights to include parts of the already published articles in the thesis. THESIS DETAILS Thesis Title: Multi-Schema-Version Data Management Ph.D. Student: Kai Herrmann Supervisors: Prof. Dr.-Ing. Wolfgang Lehner, Technische Universität Dresden Prof. Torben Bach Pedersen, Aalborg University The main body of this thesis consists of the following peer-reviewed and published papers. 1. Kai Herrmann, Hannes Voigt, Andreas Behrend, Jonas Rausch, and Wolfgang Lehner. Living in Parallel Realities: Co-Existing Schema Versions with a Bidirectional Database Evolution Lan- guage. In International Conference on Management Of Data (SIGMOD), pages 1101–1116. ACM, 2017 Input for Chapters 2 and 6 2. Kai Herrmann, Hannes Voigt, Jonas Rausch, Andreas Behrend, and Wolfgang Lehner. Robust and simple database evolution. Information Systems Frontiers, (Special issue):1–17, 2017 Input for Chapters 4 and 5 3. Kai Herrmann, Hannes Voigt, Thorsten Seyschab, and Wolfgang Lehner. InVerDa – The Liq- uid Database. In Datenbanksysteme für Business, Technologie und Web (BTW), pages 619–622. Gesellschaft für Informatik (GI), 2017 Relates to Chapter 2 4. Kai Herrmann, Hannes Voigt, Thorsten Seyschab, and Wolfgang Lehner. InVerDa – co-existing schema versions made foolproof. In International Conference on Data Engineering (ICDE), pages 1362–1365. IEEE, 2016 Relates to Chapter 2 5. Kai Herrmann, Hannes Voigt, Andreas Behrend, and Wolfgang Lehner. CoDEL – A Relationally Complete Language for Database Evolution. In European Conference on Advances in Databases and Information Systems (ADBIS), pages 63–76. Springer, 2015 Relates to Chapter 4 This thesis has been submitted for assessment in partial fulfillment of the joint Ph.D. degree. The thesis is based on the published scientific papers which are listed above. As part of the assessment, co-author statements have been made available to the assessment committee and are also available at the Technical Doctoral School of IT and Design at Aalborg University and the Faculty of Computer Science at Technische Universität Dresden. ABSTRACT Modern agile software development methods allow to continuously evolve software systems by easily adding new features, fixing bugs, and adapting the software to changing requirements and conditions while it is continuously used by the users. A major obstacle in the agile evolution is the underly- ing database that persists the software system’s data from day one on. Hence, evolving the database schema requires to evolve the existing data accordingly—at this point, the currently established solu- tions are very expensive and error-prone and far from agile. In this thesis, we present InVerDa, a multi-schema-version database system to facilitate agile database development. Multi-schema-version database systems provide multiple schema versions within the same database, where each schema version itself behaves like a regular single-schema database. Cre- ating new schema versions is very simple to provide the desired agility for database development. All created schema versions can co-exist and write operations are immediately propagated between schema versions with a best-effort strategy. Developers do not have to implement the propagation logic of data accesses between schema versions by hand, but InVerDa automatically generates it. To facilitate multi-schema-version database systems, we equip developers with a relational complete and bidirectional database evolution language (BiDEL) that allows to easily evolve existing schema versions to new ones. BiDEL allows to express the evolution of both the schema and the data both forwards and backwards in intuitive and consistent operations; the BiDEL evolution scripts are orders of magnitude shorter than implementing the same behavior with standard SQL and are even less likely to be erroneous, since they describe a developer’s intention of the evolution exclusively on the level of tables without further technical details. Having the developers’ intentions explicitly given in the BiDEL scripts further allows to create a new schema version by merging already existing ones. Having multiple co-existing schema versions in one database raises the need for a sophisticated phys- ical materialization. Multi-schema-version database systems provide full data independence, hence the database administrator can choose a feasible materialization, whereby the multi-schema-version database system internally ensures that no data is lost. The search space of possible materializations can grow exponentially with the number of schema versions. Therefore, we present an adviser that re- leases the database administrator from diving into the complex performance characteristics of multi- schema-version database systems and merely proposes an optimized materialization for a given work- load within seconds. Optimized materializations have shown to improve the performance for a given workload by orders of magnitude. We formally guarantee data independence for multi-schema-version database systems. To this end, we show that every single schema version behaves like a regular single-schema database independent of the chosen physical materialization. This important guarantee allows to easily evolve and access the database in agile software development—all the important features of relational databases, such as transaction guarantees, are preserved. To the best of our knowledge, we are the first to realize such a multi-schema-version database system that allows agile evolution of production databases with full support of co-existing schema versions and formally guaranteed data independence. 7 8 DANSK RESUMÉ (SUMMARY IN DANISH) Moderne agile software udviklings metoder gør det muligt at kontinuerligt videreudvikle software sys- temer ved at tilføje ny funktionalitet, fjerne fejl og tilpasse systemet til at opfylde nye krav samtidig med at det bliver brugt af dets brugere. En stor udfordring i den agile software udviklinger er den underliggende database der indeholder systemets data, fordi at foretage ændringer af database ske- maet kræver også at alt data bliver ændret. At foretage sådanne ændringer i nuværende etablerede løsninger er meget ressourcekrævende og risikoen for fejl er høj og hele processen er langt fra agil. I denne afhandling, præsentere vi InVerDa, en multi-skema-version database der muliggøre agil vide- reudvikling af databasen. Multi-skema-version databasesystemer har flere versioner af database ske- maet, hvor hvert skema version fungere som en standard enkelt-skema databasesystem. Det er meget simpelt at lave en ny version af et skema og det er passer godt med den agil udviklings filosofi. Flere skema version kan eksistere samtidigt og skrive operationer bliver propageret mellem alle skemaer. Software udviklerne behøver ikke at implementere datatilgang logikken mellem skema versioner, det gør InVerDa automatisk. For at facilitere multi-skema-version systemer, har vi skabt et relationelt komplet og tovejs database udviklings sprog (BiDEL), det gør det muligt og nemt at lave nye og videreudvikle eksisterende skemaer. BiDEL gør det muligt at skifte mellem sema versioner både fre- mad og bagud i tid. Endvidere, er BiDEL sproget flere størrelsesordner kortere end implementationen af samme opførelse i standard SQL. Der er også langt mindre risiko for at lave fejl ved implementerin- gen fordi sproget beskriver software udviklerens intentioner, baseret på database tabeller, uden at gå i unødige tekniske detaljer. At have software udviklernes intentioner beskrevet med BiDEL gør det muligt at kombinere eksisterende skemaer for at skema helt nye skema versioner. Det er at have flere database skema versioner i en database kræver sofistikeret fysisk materialisering af data. Multi-skema-version databasesystemer tager konceptet “data uafhængighed”
Load more

Recommended publications
  • Automated Testing of Database Schema Migrations
    DEGREE PROJECT IN COMPUTER SCIENCE AND ENGINEERING, SECOND CYCLE, 30 CREDITS STOCKHOLM, SWEDEN 2019 Automated Testing of Database Schema Migrations PETER JONSSON KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF ELECTRICAL ENGINEERING AND COMPUTER SCIENCE Automated Testing of Database Schema Migrations PETER JONSSON Master in Computer Science Date: June 28, 2019 Supervisor: Johan Gustavsson Examiner: Elena Troubitsyna School of Electrical Engineering and Computer Science Host company: The Swedish Police Authority Swedish title: Automatiserad testning av databasschemaförändringar iii Abstract Modern applications use databases, and the majority of them are relational databases, which use schemas to impose data integrity constraints. As appli- cations change, so do their databases. Database schemas are changed using migrations. Certain conditions can result in migrations failing in production environments, leading to a broken database state and testing can be problem- atic without accessing production data which can be sensitive. Two migration validation methods were proposed and implemented to au- tomatically reject invalid migrations that are not compatible with the database state. The methods were based on, and compared to, a default method that used Liquibase to structure and perform migrations. The assertion method used knowledge of what a valid state would look like to generate pre-conditions from assertions to verify that the database’s state matched expectations and that the migrations were compatible with a database’s state prior to migra- tion. The schema method, used a copy of the production database’s schema to perform migrations on an empty database in order to test the compatibility of the old and new schemas. 108 test cases consisting of a migration and a database state were used to test all methods.
    [Show full text]
  • Icpc - Local Registration System
    ICPC - LOCAL REGISTRATION SYSTEM A Project Presented to the faculty of the Department of Computer Science California State University, Sacramento Submitted in partial satisfaction of the requirements for the degree of MASTER OF SCIENCE in Computer Science by Shiva Kumar Melam FALL 2016 © 2016 Shiva Kumar Melam ALL RIGHTS RESERVED ii ICPC - LOCAL REGISTRATION SYSTEM A Project by Shiva Kumar Melam Approved by: __________________________________, Committee Chair John Clevenger, Ph.D __________________________________, Second Reader Scott Gordon, Ph.D ____________________________ Date iii Student: Shiva Kumar Melam I certify that this student has met the requirements for format contained in the University format manual, and that this project is suitable for shelving in the Library and credit is to be awarded for the project. __________________________, Graduate Coordinator ___________________ Ying Jin, Ph.D. Date Department of Computer Science iv Abstract of ICPC - LOCAL REGISTRATION SYSTEM by Shiva Kumar Melam ICPC (International Collegiate Programming Contest) is a worldwide programming contest organized by ACM (Association for Computing Machinery) every year. Over 40,000 students from over 2500 Universities all around the globe participate in this prestigious competition. It is a team based multi-tier competition which follows the rules formulated by ACM. The competition initially takes place among the local universities and the winners of this contest get selected to the regional level competition. Winners at the regional level contest advance to the world finals. Currently, the ICPC has a web-based registration system only for the regional and world finals Contests. Registration of the contestants/teams who participate in local contests has been a manual process i.e.
    [Show full text]
  • Develop Modern Applications with Oracle Database
    Develop Modern Applications with Oracle Database How Oracle Database can help you manage data in the software development life cycle and build scalable, secure applications fast. September 09, 2020 | Version 1.00 Copyright © 2020, Oracle and/or its affiliates Public PURPOSE STATEMENT This document provides an overview of Oracle Database features that help developers build applications. It is intended solely to help you assess the business benefits of using Oracle Database and to plan your development projects. INTENDED AUDIENCE This technical brief is for developers building data-driven applications. It assumes familiarity with basic database terms and the software development life cycle. DISCLAIMER This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software license and service agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.
    [Show full text]
  • Maven Plugin for Defining Sql Schema
    Maven Plugin For Defining Sql Schema Wily Nealy never nerved so synergistically or bowses any lobules crassly. Von is unanchored and job salleeforward pander as seemly not continuously Cyrus labializing enough, grossly is Wallas and misspeaking teleological? forcibly. When Obie encouraged his The library translates to install plugin sql plugin for maven schema update scripts in the maven central character bash shell script This plugin sql schemas that defines no longer pass it is plugins will define custom webapps that. Storing the most common attack in the information regarding their projects using maven for enabling query for this argument passed to relational database. Just defining identifier attribute which would become out all maven plugin for defining sql schema changes made permanent. I am setting up first liquibase maven project told a MySQL DB. Like to sql plugin execution is useful for defining different mechanisms of jdbi provides all for maven defining sql plugin schema? Both catalog and collections have created database plugin schema to apply changes are both. Format A formatter for outputting an XML document with three pre-defined. Configuring the Alfresco Maven plugin Alfresco Documentation. The installation of the MSSQL schema was pure pain there were a turn of plain SQL files which had even be. The maven for defining and define sql schemas for uuid identifier. To load SQL statements when Hibernate ORM starts add an importsql file to the. Setting up and validating your film project Using Maven. The hibernate3-maven-plugin can dash be used to toe a schema DDL from. For maven plugin creates sql schemas, you can become.
    [Show full text]
  • Getting Hip with Jhipster Frederik Hahne, WPS Management Gmbh
    Getting Hip with JHipster Frederik Hahne, WPS Management GmbH Der Scrum-Master Samu hat ein Problem. Er kann und Frameworks, konfiguriert diese nach aktuellen Best Practices nicht noch mehr Funktionen aus dem unterneh- und stellt sicher, dass die verwendeten Technologien reibungslos mensweiten Ticketsystem herausholen. Deshalb miteinander funktionieren. spielt er mit dem Gedanken, eine Web-Anwendung Da Samu für einen Prototyp keine Zeit hat, um sich in die Besonder- zu schreiben, die sich in das bestehende Ticket- heiten von Spring Security einzulesen oder in die Konfiguration von system integriert, sodass er dort spezielle Angular und Webpack einzuarbeiten, gibt er JHipster eine Chance. Er wird mit JHipster die Anwendungen hochfahren und das Datenmo- Anforderungen und Workflows implementieren dell erzeugen, damit er sich auf das Implementieren der Business- kann. Leider liegen seine Tage als Entwickler etwas logik konzentrieren kann. JHipster hilft nicht nur Anfängern, sondern weiter zurück und er hat auch keine Zeit, sich auch erfahrenen Entwicklern, schneller produktiv zu sein [17]. mit dem Schreiben von Boilerplate-Code einer JHipster in Zahlen modernen Web-Anwendung zu befassen. Zum Samu möchte auf einem aktiven und gut gepflegten Projekt auf- Glück erinnert er sich, dass die Java-Entwicklerin bauen, damit er bei Problemen und Fragen schnell Hilfe findet und Jennifer in ihrer Freizeit im JHipster-Projekt aktiv Fehler durch das Team zeitnah behoben werden können, und schaut sich die Historie des Projekts an. JHipster wurde im Jahr 2013 ge- ist. Dieser Artikel begleitet Samu dabei, wie er die startet, seitdem gab es fünf Major-Releases. Die aktuelle Version Möglichkeiten von JHipster erkundet, um einen ist 5.6.1 (November 2018).
    [Show full text]
  • Generate Java Code from Database Schema
    Generate Java Code From Database Schema pledgedwhenParlando allodial or Christorpher arms. and fallible chant, Aldrich his waxesanthropogeny some corbeille? gluttonise Aguinaldo idealises fingergood. waveringlyHow vulnerable if unturfed is David Yule At very clean and work as false, a test database queries and java code from database schema scripts to using the facilities The parse tree is database from different databases such cases the appropriate type of the relationships between objects to automatically load xml syntax to use flyway managed controllers or show the jdt. But opting out loud some skill these cookies may express an effect on your browsing experience. So as soon endorse a database schema takes advantage of an advanced DDL feature, schema migration must also use voice and this can only those done through manually created incremental scripts. The name they the haunt is displayed under the Java DB node. If enabled, the tools will reverse engineer the database defined in the connection information in the selected Hibernate Console Configuration, and generate code based on the database schema. XEP, and provides the connection to preserve database. The java classes, developers outside of a commercial database from java code database schema evolution must be projected as false, you are used at some way. Providing a department table in a school, you want all selected all your database table while working of your database from java code database schema from an existing tables. Looks very thin support? To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.
    [Show full text]
  • CI/CD for Oracle Database & APEX Developers
    CI/CD for Oracle Database & APEX Developers RMOUG Virtual Training Days 2021 Brian Spendolini Product Manager Oracle Database Development Tools @btspendo btspendo https://blogs.oracle.com What is CI/CD? 2 Copyright © 2020, Oracle and/or its affiliates What is CI/CD and Why do we need it? CI/CD is continuous integration, continuous delivery, and continuous deployment • Introduces automation into all stages of app/database development • Helps developers work on the same app and merge their code changes back to a shared branch frequently • Development changes are automatically tested on push/commits and merges Why? • Consistency/Repeatability • Accountability • Security • Standardization • Find Issues Faster/Better Code/Quality Releases • More Frequent Releases 3 Copyright © 2020, Oracle and/or its affiliates CI/CD with the database and APEX? Traditionality this has been hard. Why? • APEX/DB bucks the trend of isolated development environments • Dev instances can be expensive • Licensing issues • DB/APEX changes are different from traditional files/code seen with DevOPs and CI/CD processes • Metadata driven • Versioning or lack there of • Rollback issues • Very manual process and a lot of individual accountability • DB change tracking • APEX change tracking • Isn't DevOps for those new-fangled development languages only? 4 Copyright © 2020, Oracle and/or its affiliates CI/CD with the database and APEX? We can fix it? Yes, we can! Centralized code repository no more big zips or wiki pages with attachments Individual code branches Individual
    [Show full text]
  • Technology Profile
    2021 Technology Profile https://azati.ai +375 (29) 6845855 Belarus, 31 K. Marks Street, Sections 5-6 Grodno, 230025 1 Table Of Contents TABLE OF CONTENTS page 01 DEPLOYMENT, BI & DATA page 09 WAREHOUSING GENERAL INFORMATION page 02 DATA SCIENCE & MACHINE LEARNING page 10 JAVA TECHNOLOGIES page 03 MONITORING TOOLS, PORTALS & SOLUTIONS, page 11 VERSION CONTROL RUBY & JAVASCRIPT TECHNOLOGIES page 04 VERSION CONTROL, SDK & OTHER TOOLS page 12 WEB & PHP TECHNOLOGIES page 05 OTHER TOOLS page 13 MOBILE DEVELOPMENT & DATABASES page 06 SOFTWARE TESTING & QA page 07 APPLICATION DEPLOYMENT page 08 2 General Information 01 PROGRAMMING LANGUAGES: 02 MARK-UP AND MODELING 05 SOFTWARE ARCHITECTURE PATTERNS: LANGUAGES: Java Representational State Transfer (REST/RESTful) JavaScript (ES5/ES6) HTML (4/5) Model-View-Controller (MVC) PHP XSLT Microservices TypeScript UML GraphQL PL/SQL Kotlin Smalltalk C 03 PROJECT MANAGEMENT C++ METHODOLOGIES: C# Agile (Kanban/SCRUM) Groovy Waterfall Delphi Behavior-driven development (BDD) Pascal Test-driven development (TDD) Python Feature-driven development (FDD) SQL Ruby R CoffeeScript 04 DEVELOPMENT APPROACHES: Perl Continuous Delivery (CD) Bash Continuous Integration (CI) Shell 3 Java Technologies 06 JAVA TECHNOLOGIES: 07 JAVA FRAMEWORKS: Apache POI Java (7/8/9) Spring Apache Wicket Java Servlet Spring Boot Apache CXF Java Database Connectivity (JDBC) Spring REST Apache Shiro Java REST Spring MVC Apache Camel Java Persistence API (JPA) Spring Data Java Message Service (JMS) Spring Security 08 JAVA LIBRARIES: JBoss Drools
    [Show full text]
  • Gradle Beyond the Basics
    Gradle Beyond the Basics Tim Berglund Gradle Beyond the Basics by Tim Berglund Copyright © 2013 Gradle, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/ institutional sales department: 800-998-9938 or [email protected]. Editors: Mike Loukides and Meghan Blanchette Cover Designer: Randy Comer Production Editor: Kara Ebrahim Interior Designer: David Futato Proofreader: Kara Ebrahim Illustrator: Rebecca Demarest July 2013: First Edition Revision History for the First Edition: 2013-07-15: First release See http://oreilly.com/catalog/errata.csp?isbn=9781449304676 for release details. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Gradle Beyond the Basics, the image of a Belgian shepherd dog, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a trade‐ mark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. ISBN: 978-1-449-30467-6 [LSI] Table of Contents Preface.
    [Show full text]
  • Database Refactoring with Liquibase
    Database Refactoring with Liquibase Michael Le Feuvre, OnBelay Consulting Agenda • What is Database refactoring • Introducing Liquibase • Liquibase example • Questions OnBelay Consulting 2 Database Refactoring Evolutionary change OnBelay Consulting 3 Traditional approach • Traditional approach to changing the database schema. • Make an appointment to see the DBA. • Plead that you want to add a column to an existing table • DBA considers your request • Decides to grant it but first must update the ER diagram in a horribly expensive Database Architecture and Design tool that maintains a logical data model. The model is then rendered in to a physical model. Great for wall charts. • DBA generates or hand-codes the database changes into SQL scripts. • DBA then updates each database directly that requires the changes. OnBelay Consulting 4 Consequences of traditional approach • Because the overhead in the traditional process is so onerous, many organizations required that database design be done up front so that the database was “ready” for programmers to use. • Database artifacts may not be in source control. • If database objects are in source control they aren’t necessarily in the same repository as the application source code. application code changes and database changes are not committed together in the same commit. • The above process is entirely antithetical to an Agile development process and since the database requirements must be known in advance of starting development • Most organizations manage database changes somewhere between traditional and database refactoring. OnBelay Consulting 5 Database refactoring • Based on the concept of refactoring popularized by Martin Fowler: • described as a “refactoring as a small change to your source code that improves its design without changing its semantics.” (Refactoring, Martin, James, 1999) • Evolutionary approaches to database maintenance have been discussed since the 2000’s.
    [Show full text]
  • Enlighten Whitepaper Template
    Big Data Analytics In M2M WHITE PAPER Cloud Ready Web Applications Big Data Analytics In M2M with jHipster WHITE PAPER Table of Contents Introduction ...................................................................................... 3 Key Architecture Drivers ................................................................... 3 What is jHipster? ............................................................................... 4 Technology behind JHipster .............................................................. 4 Creating a jHipster Application ......................................................... 4 Client Side Technologies ................................................................... 6 Startup Screen ................................................................................... 8 Server Side Technologies .................................................................. 9 Spring Data JPA ............................................................................... 10 Spring Data REST ............................................................................. 10 Swagger UI ...................................................................................... 10 Spring Boot ...................................................................................... 11 Spring Boot Actuator ....................................................................... 12 Logging ............................................................................................ 15 Liquibase ........................................................................................
    [Show full text]
  • Oracle-Sql-Developer-Users-Guide.Pdf
    Oracle® SQL Developer User's Guide Release 19.2 F20349-01 August 2019 Oracle SQL Developer User's Guide, Release 19.2 F20349-01 Copyright © 2006, 2019, Oracle and/or its affiliates. All rights reserved. Primary Author: Celin Cherian Contributing Authors: Chuck Murray 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 li‐ cense 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 engi‐ neering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibit‐ ed. 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-spe‐ cific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the pro‐ grams, 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]