Integration of Spatial Vector Data in Enterprise Relational Database Environments

Total Page:16

File Type:pdf, Size:1020Kb

Integration of Spatial Vector Data in Enterprise Relational Database Environments Integration of Spatial Vector Data in Enterprise Relational Database Environments Dissertation zur Erlangung des akademischen Grades Doktor-Ingenieur (Dr.-Ing.) vorgelegt dem Rat der Fakult¨at f¨ur Mathematik und Informatik der Friedrich-Schiller-Universit¨at Jena im Juli 2006 von Dipl.-Inf. Knut Stolze geboren am 8. Januar 1975 in Jena, Th¨uringen Gutachter: 1. Prof. Dr. Klaus K¨uspert, Friedrich-Schiller-University Jena 2. Prof. Johann-Christoph Freytag, Ph.D., Humboldt-Universit¨at zu Berlin 3. Dr. Albert Maier, IBM Deutschland Entwicklung GmbH, B¨oblingen Tag der letzten Pr¨ufung des Rigorosums: 7. November 2006 Tag der ¨offentlichen Verteidigung: 10. November 2006 ii To My Wife Annett iv Abstract Spatial and geometric data can be found in virtually every relational database. Such data is often not explicitly modeled but rather hidden in addresses, for example. Unless spatial data is treated as first class citizen in the relational database management systems (RDBMSs), spatial features cannot be leveraged and exploited by applications to their full extent. Several products provide the capabilities to store and query geometric data directly in relational databases. Those products include dedicated data types along with associated spatial functions and indexing mechanisms. The SQL/MM spatial standard exists to ensure that the spatial interface provided by products are compatible. The standard covers basic spatial functionality only. Data types are defined and include a set of routines that are used to construct spatial values from external data formats, compare two geometries regarding their spatial relationship, generate new geometries, or to extract spatial properties. However, more advanced func- tionality is crucial for applications and their business logic is still lacking. Therefore, ap- plications either disregard spatial information completely or noticeable effort is invested for the addition of customized spatial logic. This thesis is dedicated to closing the most significant gaps in the standard that we identified to further broaden the user base. The first issue addressed in the thesis is the insufficient support of spatial data types in programming languages and the respective database connectivity mechanisms, most prominently Java and JDBC. We extend the JDBC interface to incorporate a spatial class hierarchy. Instances of these classes can be directly retrieved from the RDBMS or passed to it, avoiding the current clumsy and time-consuming stream-based interface. Other major enhancements to the standard that are contributed by this thesis are graph and network related routines. We exploit the topological properties of geometries for functions that implement graph algorithms while treating graphs transparently as in- dexing structures for geometries only. Shortest path or traveling salesman problems can be solved directly on street networks. The results are in a relational fashion so that they can even be combined with data from other tables in the database. The SQL/MM spatial standard is only concerned with two-dimensional data. This is in- sufficient. Many applications require at least a third dimension, for instance CAD/CAM. We develop and implement the concepts for the integration of 3D geometries into the standard. This work also comprises the necessary considerations for operations in true three-dimensional data space. Enterprises operate diverse database systems and architectures. It is important to es- tablish transparent access to spatial and non-spatial data alike in such environments. Federation and replication are two mechanisms to provide such access in distributed sys- tems. We develop the techniques to integrate spatial data in federation and replication setups while relying on the available products only. This restriction is based on the fact that new and independent solutions and prototypes are usually not an option in more complex configurations. Kurzfassung (German Abstract) R¨aumliche und geometrische Daten existieren in praktisch jeder relationalen Datenbank. Diese Daten sind jedoch oft nicht explizit modelliert, sondern z. B. in Adressen versteckt. Aber nur die explizite Modellierung erlaubt die Nutzung der r¨aumlichen Eigenschaften durch Applikationen. Verschiedene Produkte stellen Funktionalit¨at zur direkten Verwal- tung von r¨aumlichen Daten in relationalen Datenbanken zur Verfugung.¨ Es sind dedi- zierte Datentypen, sowie zugeh¨orige Routinen und Indexmechanismen implementiert. Zur Harmonisierung der Schnittstellen besagter Produkte wurde die SQL/MM Spati- al Norm entwickelt. Allerdings definiert die Norm nur Grundfunktionalit¨at. So existie- ren Datentypen und zugeh¨orige Routinen fur¨ die Konvertierung zwischen Geometrien und zeichenbasierten externen Datenformaten, Routinen zum Vergleich zweier Geome- trien gem¨aß ihrer r¨aumlichen Beziehung, Routinen zum Erzeugen neuer Geometrien und Routinen zum Extrahieren von r¨aumlichen Eigenschaften. Fur¨ Anwendungen sind aber h¨ohere und komplexere Funktionen notwendig, damit r¨aumlichen Daten nahtlos integriert werden k¨onnen. Diese Arbeit widmet sich den wichtigsten dieser Lucken¨ und macht Vorschl¨age, um sie baldigst in der Norm zu schließen. Ein vordringliches Problem besteht bereits bei der direkten Einbindung der r¨aumlichen Daten in die Schnittstellen zwischen Datenbanksystem und Anwendung, z. B. Java und JDBC. JDBC wird um eine Klassenhierarchie fur¨ r¨aumlichen Daten erweitert. Instanzen dieser Klassen k¨onnen direkt zwischen Anwendung und RDBMS ausgetauscht werden. Weitere Modifikationen der SQL/MM Spatial Norm beziehen sich auf Graphen und Netzwerkoperationen. Die topologischen Eigenschaften von Geometrien werden fur¨ neue Funktionen ausgenutzt, wobei die Graphen transparent als Indexstrukturen Anwendung finden. Somit k¨onnen kurzeste¨ Pfade berechnet oder das Traveling-Salesman-Problem direkt auf den gespeicherten Straßendaten gel¨ost werden. Die Ergebnisse werden in relationaler Form aufgebaut, so dass sie direkt mit anderen Daten in der Datenbank verbunden werden k¨onnen. Die SQL/MM Spatial Norm bezieht sich ausschließlich auf zwei-dimensionale r¨aumliche Daten. Fur¨ CAD/CAM Applikationen ist dies z. B. unzureichend, und zumindest eine weitere Dimension ist notwendig. Die Konzepte fur¨ die Integration von 3D Objekten in die Norm werden entwickelt und erprobt. Dies umfasst auch die Erweiterung aller bereits vorhandener Operationen fur¨ den drei-dimensionalen Raum. Viele verschiedene Datenbanksysteme und Architekturen finden in kommerziellen Pro- duktionsumgebungen Einsatz. Transparenter Zugriff auf r¨aumliche und nicht-r¨aumliche Daten ist in solchen Umgebungen essentiell. F¨oderation und Replikation sind zwei Me- chanismen, um Daten zwischen den Komponenten verteilter Systeme auszutauschen. Diese Arbeit entwickelt die Techniken, um r¨aumliche Daten in diese Prozesse zu inte- grieren, da sie bisher vernachl¨assigt wurden. Dabei wird gezielt auf die M¨oglichkeiten existierender Produkte gebaut, weil neue L¨osungen und Prototypen ublicherweise¨ nicht sicher in solch komplexen Konfiguration einzusetzen sind. Contents List of Figures xiii List of Tables xvii List of Listings xix Preface xxi I Basics 1 1 Introduction 3 2 Concerning Spatial Data 9 2.1 SpatialData.................................. 10 2.1.1 TypesofGeometricPrimitives. 10 2.1.2 SpatialReferenceSystems . 11 2.1.3 PropertiesofGeometries . 15 2.2 Object-RelationalFeaturesinSQL:2003 . ..... 16 2.3 TheSQL/MMSpatialStandard . 19 2.3.1 History................................. 20 2.3.2 SpatialTypeHierarchy. 22 2.3.3 MethodsontheSpatialTypes . 25 2.3.4 SupportingDataTypes. 28 2.3.5 SpatialInformationSchema . 29 2.3.6 SampleUsageScenarios . 31 2.3.7 DiscussionoftheStandard. 35 2.3.8 Improved Spatial Type Hierarchy . 39 2.3.9 MajorGapsintheStandard . 43 2.4 GeographyMarkupLanguage . 44 2.5 Products Implementing Spatial Extensions . ...... 46 2.5.1 IBM DB2 Spatial and Geodetic Extenders . 46 2.5.2 IBMInformixSpatialDataBlade . 48 vii Contents 2.5.3 MapInfoSpatialWare. 49 2.5.4 MySQLSpatial ............................ 50 2.5.5 OracleSpatial............................. 51 2.5.6 PostgreSQL&PostGIS. 52 II Functional Enhancements for SQL/MM 53 3 Spatial Application Development 55 3.1 SpatialSupportinJDBC........................... 56 3.2 SpatialTransformGroups . 58 3.2.1 ST WellKnownText TransformGroup. 59 3.2.2 ST WellKnownBinary TransformGroup . 60 3.2.3 ST GML TransformGroup. .. .. 61 3.2.4 Transforms for Application Bindings . .. 63 3.3 EnhancementstoJDBC ........................... 63 3.3.1 SpatialClassHierarchy. 64 3.3.2 Extending the Interface ResultSet .................. 66 3.3.3 Extending the Interface PreparedStatement ............ 66 3.3.4 Extending the Interface CallableStatement ............. 68 3.3.5 Prototypical Implementation . 69 3.3.6 Conclusions for the Extended JDBC Driver . 74 3.4 Summary ................................... 75 4 Integration of Graph Functionality 77 4.1 GraphConcepts................................ 79 4.1.1 Definitions............................... 79 4.1.2 Algorithms .............................. 80 4.2 Literature&ProductOverview . 83 4.3 Mappings Between Geometries and Graphs . ... 85 4.3.1 Building Graphs from Linestrings . 85 4.3.2 Building Graphs from Point Geometries . 95 4.3.3 BuildingGraphsfromPolygons . 98 4.3.4 ImpactonGraphAlgorithms . 100 4.4 TheSpatialGraphExtenderforDB2 . 102 4.4.1 Requirements ............................. 102 4.4.2 Architecture.............................. 103 4.4.3 GraphsConstruction . 106 4.4.4 UpdatingGraphs . .. .. .. 111
Recommended publications
  • Mapinfo Professional Data Sheet
    PRODUCT DATA SHEET MapInfo Professional® v12 Location-powered Decision-making Made Easy woRK SMARTER, NOT HARDER, WITH THE PREMIER LOCATION INTELLIGENCE SOLUTION Product Overview EXPECTED ROI Data is used every day, and across every enterprise, to make critical strategic decisions With MapInfo Professional, you that positively impact both business and customers alike. MapInfo Professional v12 and its location intelligence capabilities helps organisations understand their business, can visualise the relationships analyse trends geographically, and make critical decisions with greater clarity of risk between data and geography. and opportunity. Business analysts, planners, GIS professionals —even non-GIS With MapInfo Professional v12, Pitney Bowes Software makes it even easier to visualise users— can gain new insights into potential, whether it’s a crime hotspot or the ideal location for a new bank branch. their markets, improve strategic A Microsoft® Windows®-based mapping application, MapInfo Professional v12 helps business analysts and GIS professionals visualise and share the relationships between decision-making and share data and geography. information-rich maps and graphs. MapInfo Professional v12 makes it easier than ever to create great looking maps. With “MapInfo Professional cuts the time new cartographic output features such as enhanced automatic labelling options, new by 25 percent that it takes to audit our scalebar enhancements, and greater flexibility over legend and layout objects, making network of banking centres, along maps that stand out has never been so easy. with easily mapping and analysing With v12, users can also keep up to date with news from the MapInfo world, thought their geospatial measurements.” leadership articles, events and new product releases directly within MapInfo Scott Weston Professional.
    [Show full text]
  • Filemaker 16 ODBC and JDBC Guide
    FileMaker®16 ODBC and JDBC Guide © 2004–2017 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker, FileMaker Go, and the file folder logo are trademarks of FileMaker, Inc. registered in the U.S. and other countries. FileMaker WebDirect and FileMaker Cloud are trademarks of FileMaker, Inc. All other trademarks are the property of their respective owners. FileMaker documentation is copyrighted. You are not authorized to make additional copies or distribute this documentation without written permission from FileMaker. You may use this documentation solely with a valid licensed copy of FileMaker software. All persons, companies, email addresses, and URLs listed in the examples are purely fictitious and any resemblance to existing persons, companies, email addresses, or URLs is purely coincidental. Credits are listed in the Acknowledgments documents provided with this software. Mention of third-party products and URLs is for informational purposes only and constitutes neither an endorsement nor a recommendation. FileMaker, Inc. assumes no responsibility with regard to the performance of these products. For more information, visit our website at http://www.filemaker.com. Edition: 01 Contents Chapter 1 Introduction 5 About this guide 5 Where to find FileMaker documentation 5 About ODBC and JDBC 6 Using FileMaker software as an ODBC client application 6 Importing ODBC data 6 Adding ODBC tables to the relationships graph 6 Using a FileMaker database as a data source 7 Accessing a
    [Show full text]
  • Chapter 3 DB Gateways.Pptx
    Prof. Dr.-Ing. Stefan Deßloch AG Heterogene Informationssysteme Geb. 36, Raum 329 Tel. 0631/205 3275 [email protected] Chapter 3 DB-Gateways Outline n Coupling DBMS and programming languages n approaches n requirements n Programming Model (JDBC) n overview n DB connection model n transactions n Data Access in Distributed Information System Middleware n DB-Gateways n architectures n ODBC n JDBC n SQL/OLB – embedded SQL in Java n Summary 2 © Prof.Dr.-Ing. Stefan Deßloch Middleware for Information Systems Coupling Approaches – Overview n Static Embedded SQL n static SQL queries are embedded in the programming language n cursors to bridge so-called impedance mismatch n preprocessor converts SQL into function calls of the programming language n potential performance advantages (early query compilation) n vendor-specific precompiler and target interface n resulting code is not portable n Dynamic Embedded SQL n SQL queries can be created dynamically by the program n character strings interpreted as SQL statements by an SQL system n preprocessor is still required n only late query compilation n same drawbacks regarding portability as for static embedded n Call-Level Interface (CLI) n standard library of functions that can be linked to the program n same capabilities as (static and dynamic) embedded n SQL queries are string parameters of function invocation n avoids vendor-specific precompiler, allows to write/produce binary-portable programs 3 © Prof.Dr.-Ing. Stefan Deßloch Middleware for Information Systems Coupling Approaches (Examples)
    [Show full text]
  • Mapinfo Professional®
    MapInfo Professional® Comprehensive insight for location-powered decision making and data analysis Technology MapInfo Professional Powerful analysis tools are simple and easy to use. Through a simple user interface, you’ll automatically generate Voronoi polygons, Increase revenue, lower costs, boost efficiency and improve a complex and powerful analysis tool that allows you to easily analyze retail trade areas, cellular service areas, voter registration districts or risk analysis reports. The Split-by-Line/Polyline feature easily divides up areas under examination using a street, a utility service line, service with location-based intelligence or any line at all. For instance, comparing 911 response times above or below a river or roadway, is now one easy operation. Access data from any business-standard database. MapInfo Professional supports Oracle, Microsoft and IBM. In addition, MapInfo MapInfo Professional helps organizations make better, more informed Professional can read and write Oracle Spatial™® data types and directly access data stored in Microsoft SQL Server 2008. With MapInfo decisions about their customers, assets and operations, resulting in Professional, spatial data – points, lines and areas (polygons) – are accessed, stored and protected like any other data in the database. Pitney Bowes Business Insight has partnered with Safe Software to offer FME. This add-on to MapInfo Professional allows users to access improved operating performance, reduced operating costs and increased over 150 GIS data formats directly. return on investment (ROI). These gains are made almost automatically, Publish information faster and in more formats. Business and government are both under pressure to get better information out by appealing to the innate human ability to visualize information.
    [Show full text]
  • Mapbasic User Guide, Mapbasic’S Documentation Set Includes the Mapbasic Reference, and Online Help System
    MapBasic 11.5 USER GUIDE Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor or its representatives. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, without the written permission of Pitney Bowes Software Inc., One Global View, Troy, New York 12180-8399. © 2012 Pitney Bowes Software Inc. All rights reserved. Pitney Bowes Software Inc. is a wholly owned subsidiary of Pitney Bowes Inc. Pitney Bowes, the Corporate logo, MapInfo, Group 1 Software, and MapBasic are trademarks of Pitney Bowes Software Inc. All other marks and trademarks are property of their respective holders. United States: Canada: Phone: 518.285.6000 Phone: 416.594.5200 Fax: 518.285.6070 Fax: 416.594.5201 Sales: 800.327.8627 Sales: 800.268.3282 Government Sales: 800.619.2333 Technical Support:.518.285.7283 Technical Support: 518.285.7283 Technical Support Fax: 518.285.7575 Technical Support Fax: 518.285.7575 www.pb.com/software www.pb.com/software Europe/United Kingdom: Asia Pacific/Australia: Phone: +44.1753.848.200 Phone: +61.2.9437.6255 Fax: +44.1753.621.140 Fax: +61.2.9439.1773 Technical Support: +44.1753.848.229 Technical Support: 1.800.648.899 www.pitneybowes.co.uk/software www.pitneybowes.com.au/software Contact information for all Pitney Bowes Software Inc. offices is located at: http://www.pbinsight.com/about/contact-us. © 2012 Adobe Systems Incorporated. All rights reserved. Adobe, the Adobe logo, Acrobat and the Adobe PDF logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
    [Show full text]
  • SWUTC/11/161142-1 Evaluation of Mobile Source Greenhouse Gas Emissions for Assessment of Traffic Management Strategies August 20
    Technical Report Documentation Page 1. Report No. 2. Government Accession No. 3. Recipient's Catalog No. SWUTC/11/161142-1 4. Title and Subtitle 5. Report Date Evaluation of Mobile Source Greenhouse Gas Emissions August 2011 for Assessment of Traffic Management Strategies 6. Performing Organization Code 7. Author(s) 8. Performing Organization Report No. Qinyi Shi and Lei Yu Report 161142-1 9. Performing Organization Name and Address 10. Work Unit No. (TRAIS) Texas Southern University 3100 Cleburne Avenue 11. Contract or Grant No. Houston, TX 77004 10727 12. Sponsoring Agency Name and Address 13. Type of Report and Period Covered Southwest Region University Transportation Center Research Report Texas Transportation Institute September 2009 – August 2011 Texas A&M University System 14. Sponsoring Agency Code College Station, Texas 77843-3135 15. Supplementary Notes Supported by general revenues from the State of Texas. 16. Abstract In recent years, there has been an increasing interest in investigating the air quality benefits of traffic management strategies in light of challenges associated with the global warming and climate change. However, there has been a lack of systematic effort to study the impact of a specific traffic management strategy on mobile source Greenhouse Gas (GHG) emissions. This research is intended to evaluate mobile source GHG emissions for traffic management strategies, in which a Portable Emission Measurement System (PEMS) is used to collect the vehicle’s real-world emission and activity data, and a Vehicle Specific Power (VSP) based modeling approach is used as the basis for emission estimation. Three traffic management strategies are selected in this research, including High Occupancy Vehicle (HOV) lane, traffic signal coordination plan, and Electronic Toll Collection (ETC).
    [Show full text]
  • Preview JDBC Tutorial
    About the Tutorial JDBC API is a Java API that can access any kind of tabular data, especially data stored in a Relational Database. JDBC works with Java on a variety of platforms, such as Windows, Mac OS, and the various versions of UNIX. Audience This tutorial is designed for Java programmers who would like to understand the JDBC framework in detail along with its architecture and actual usage. Prerequisites Before proceeding with this tutorial, you should have a good understanding of Java programming language. As you are going to deal with RDBMS, you should have prior exposure to SQL and Database concepts. Copyright & Disclaimer Copyright 2015 by Tutorials Point (I) Pvt. Ltd. All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish any contents or a part of contents of this e-book in any manner without written consent of the publisher. We strive to update the contents of our website and tutorials as timely and as precisely as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt. Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our website or its contents including this tutorial. If you discover any errors on our website or in this tutorial, please notify us at [email protected] i Table of Contents About the Tutorial ....................................................................................................................................
    [Show full text]
  • PRODUCT DATA Sheet
    PRODUCT DATA SHEET MapInfo Professional® v12 Version Comparison WORK SMARTER, NOT HARDER, WITH THE PREMIER LOCATION INTELLIGENCE SOLUTION How Does v12 Compare to Previous Versions? SUMMARY MapInfo Professional v12 adds: With MapInfo Professional Extensively Improved Labeling Capabilities v12 we make it even easier to • Better placement of curved labels visualize potential, whether – More curved labels placed on a map due to improved label placement algorithm it is for a public service, a – Auto-position option determines better positioning of a curved label – Can click and drag curved labels crime-scene hotspot, or the – When dragging curved labels, polyline highlights to provide visual feedback ideal location for a new bank – Fallback to rotated labels where data lines are too jagged or curved label can’t fit branch or retail outlet. A ® ® • Better placement of region labels Microsoft Windows -based – Auto-positioning algorithm to find a best location for a label mapping application, MapInfo – Region labels can be confined within the polygon Professional v12 helps – Automatically use different font sizes to make labels fit within a region business analysts and GIS – Use abbreviations to fit more labels on a map professionals visualize and – Automatic positioning of labels with callouts when they will not fit within a region share the relationships between data and geography. Add on Layer Control Enhancements Premium Services and out-of- • Redesigned Layer Properties dialog to provide better user experience with labeling options the-box connectivity to MapInfo and rules Manager’s data management • New right-click menu item to clear custom labels for one layer at a time capabilities, and v12 continues to set the standard for easy to use • New dialog to set layer priorities/importance for labeling mapping data creation, editing, • New right-click menu item to select all objects from a layer visualization and analysis.
    [Show full text]
  • Mapinfo Professional
    MapInfo Professional Version 9.0 USER GUIDE Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor or its representatives. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, without the written permission of MapInfo Corporation, One Global View, Troy, New York 12180-8399. © 2007 MapInfo Corporation. All rights reserved. MapInfo, the MapInfo logo, MapBasic, and MapInfo Professional are trademarks of MapInfo Corporation and/or its affiliates. MapInfo Corporate Headquarters: Voice: (518) 285-6000 Fax: (518) 285-6070 Sales Info Hotline: (800) 327-8627 Government Sales Hotline: (800) 619-2333 Technical Support Hotline: (518) 285-7283 Technical Support Fax: (518) 285-6080 Contact information for all MapInfo offices is located at: http://www.mapinfo.com/contactus. Adobe Acrobat® is a registered trademark of Adobe Systems Incorporated in the United States. Products named herein may be trademarks of their respective manufacturers and are hereby recognized. Trademarked names are used editorially, to the benefit of the trademark owner, with no intent to infringe on the trademark. libtiff © 1988-1995 Sam Leffler, copyright © Silicon Graphics, Inc. libgeotiff © 1995 Niles D. Ritter. Portions © 1999 3D Graphics, Inc. All Rights Reserved. HIL - Halo Image Library © 1993, Media Cybernetics Inc. Halo Imaging Library is a trademark of Media Cybernetics, Inc. Portions thereof LEAD Technologies, Inc. © 1991-2003. All Rights Reserved. Portions © 1993-2005 Ken Martin, Will Schroeder, Bill Lorensen. All Rights Reserved. ECW by ER Mapper © 1993-2005 VM Grid by Northwood Technologies, Inc., a Marconi Company © 1995-2005.
    [Show full text]
  • Java Database Connectivity (JDBC)
    MODULE - V Java Database Connectivity (JDBC) MODULE 5 Java Database Connectivity (JDBC) Module Description Java Database Connectivity (JDBC) is an Application Programming Interface (API) used to connect Java application with Database. JDBC is used to interact with the various type of Database such as Oracle, MS Access, My SQL and SQL Server and it can be stated as the platform-independent interface between a relational database and Java programming. This JDBC chapter is designed for Java programmers who would like to understand the JDBC framework in detail along with its architecture and actual usage. iNurture’s Programming in Java course is designed to serve as a stepping stone for you to build a career in Information Technology. Chapter 5.1 Introduction to JDBC Chapter 5.2 Setting up a Java Database Connectivity Chapter Table of Contents Chapter 5.1 Introduction to JDBC Aim ..................................................................................................................................................... 255 Instructional Objectives ................................................................................................................... 255 Learning Outcomes .......................................................................................................................... 255 5.1.1 Database Connectivity ............................................................................................................ 256 Self-assessment Questions .....................................................................................................
    [Show full text]
  • Mapinfo Mapbasic V17.0 User Guide
    MapBasic Version 17.0 User Guide Notices Copyright © April 2018 Pitney Bowes Software Inc. Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor or its representatives. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, without the written permission of Pitney Bowes Software Inc., One Global View, Troy, New York 12180-8399. © 2018 Pitney Bowes Software Inc. All rights reserved. Pitney Bowes Software Inc. is a wholly owned subsidiary of Pitney Bowes Inc. Pitney Bowes, the corporate logo, MapInfo, Group 1 Software, and MapBasic are trademarks of Pitney Bowes Software Inc. All other marks and trademarks are property of their respective holders. Contact information for all Pitney Bowes Software Inc. offices is located at: http://www.pitneybowes.com/us/contact-us.html. © 2018 OpenStreetMap contributors, CC-BY-SA; see OpenStreetMap http://www.openstreetmap.org (license available at www.opendatacommons.org/licenses/odbl) and CC-BY-SA http://creativecommons.org/licenses/by-sa/2.0 libtiff © 1988-1997 Sam Leffler, © 2018 Silicon Graphics International, formerly Silicon Graphics Inc. All Rights Reserved. libgeotiff © 2018 Niles D. Ritter. Amigo, Portions © 1999 Three D Graphics, Inc. All Rights Reserved. Halo Image Library © 1993 Media Cybernetics Inc. All Rights Reserved. Portions thereof LEAD Technologies, Inc. © 1991-2018. All Rights Reserved. Portions © 1993-2018 Ken Martin, Will Schroeder, Bill Lorensen. All Rights Reserved. ECW by ERDAS © 1993-2018 Intergraph Corporation, part of Hexagon Geospatial AB and/or its suppliers. All rights reserved.
    [Show full text]
  • Java Database Connectivity (JDBC) J2EE Application Model
    Java DataBase Connectivity (JDBC) J2EE application model J2EE is a multitiered distributed application model client machines the J2EE server machine the database or legacy machines at the back end JDBC API JDBC is an interface which allows Java code to execute SQL statements inside relational databases Java JDBC driver program connectivity for Oracle data processing utilities driver for MySQL jdbc-odbc ODBC bridge driver The JDBC-ODBC Bridge ODBC (Open Database Connectivity) is a Microsoft standard from the mid 1990’s. It is an API that allows C/C++ programs to execute SQL inside databases ODBC is supported by many products. The JDBC-ODBC Bridge (Contd.) The JDBC-ODBC bridge allows Java code to use the C/C++ interface of ODBC it means that JDBC can access many different database products The layers of translation (Java --> C --> SQL) can slow down execution. The JDBC-ODBC Bridge (Contd.) The JDBC-ODBC bridge comes free with the J2SE: called sun.jdbc.odbc.JdbcOdbcDriver The ODBC driver for Microsoft Access comes with MS Office so it is easy to connect Java and Access JDBC Pseudo Code All JDBC programs do the following: Step 1) load the JDBC driver Step 2) Specify the name and location of the database being used Step 3) Connect to the database with a Connection object Step 4) Execute a SQL query using a Statement object Step 5) Get the results in a ResultSet object Step 6) Finish by closing the ResultSet, Statement and Connection objects JDBC API in J2SE Set up a database server (Oracle , MySQL, pointbase) Get a JDBC driver
    [Show full text]