DOCSLIB.ORG

The ADO .NET Class Library Activex Data Objects .NET Is in Some Ways a Misnomer. It Implies That

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The ADO .NET Class Library Activex Data Objects .NET Is in Some Ways a Misnomer. It Implies That 04Chap.fm Page 77 Monday, November 25, 2002 9:15 PM C HAPTER 4 The ADO .NET Class Library ActiveX Data Objects .NET is in some ways a misnomer. It implies that ADO .NET is implemented as an ActiveX object library, the same way as ADO was. In a sense this is true, because like ADO, ADO .NET wraps the OLEDB COM classes. However, unlike ADO, ADO .NET is not itself an ActiveX object library. It is implemented as a collection of .NET classes. ADO .NET also has a high-performance native mode for SQL Server that does not use OLEDB at all! The basis for ADO .NET is XML. Perhaps it should have been called XDO for XML Data Objects. As we dissect the class library, you will see why. ADO .NET CLASS LIBRARY OVERVIEW The central class in ADO .NET is the DataSet. While it is tempting to com- pare the DataSet to the ADO RecordSet object, it is really a different type of object entirely. The ADO .NET DataSet is really a repository for XML data. ADO .NET has more to do with reading and persisting XML data than it does accessing databases. Instead of its primary function being to access data- bases, its primary function is to access, store, and save XML documents from many different sources. The database is just one of those sources. Data is per- sisted as World Wide Web Consortium (W3C)–compliant XML, so any con- sumer complying with the standard, no matter the platform, can use it. The DataSet can be used as a stand-alone object for storing any data you can imagine. It is also designed to be the remoting agent of choice. Since it is designed to read any XML data stream, it uses this method for marshalling data between remote sources and local programs. 77 04Chap.fm Page 78 Monday, November 25, 2002 9:15 PM 78 Chapter 4 • The ADO .NET Class Library The DataSet is composed of a collection of tables, relations, and con- straints. Does anyone remember the in-memory database that was supposed to be released with Windows 2000 and then was pulled from the release at the last minute? Well here it is, reincarnated as the DataSet. That’s right, the class has all the power you need for an in-memory database, including tables, indexes, foreign keys, and DRI. It can draw its data from a database, or you can use it as a stand-alone in-memory data cache that can be persisted to disk or sent over the network. The other main classes are for connecting to and running queries on data- bases. There are two main branches to the class library, the SqlClient classes and the OleDbClient classes. As we said before, SqlClient is optimized for SQL Server 7.0 and later databases. It uses native access and does not require OLEDB. The OleDbClient classes use the OLEDB data providers. They can be used for Oracle, Access, and any other supported database except ODBC. There is a special version of the OLEDB ODBC driver available for down- load from the Microsoft site. More on that later. Connection Class The connection classes provide the means to connect to the database. They also manage transactions, and connection pooling. The various parameters for connecting to a database are set via the ConnectionString property. In previous versions of ADO, most of the ConnectionString values were exposed through properties. For security reasons, ADO .NET only exposes the ConnectionString. We will enumerate the details of the various values of the ConnectionString in the chapter on the Connec- tion object. Command Class The Command class provides methods for storing and executing SQL state- ments and stored procedures. It has a Parameters collection that is used to pass parameters into and out of stored procedures. The collection can also be used to set the parameters for a parameterized SQL statement. The Data- Adapter class contains four Command classes for selecting, updating, insert- ing, and deleting data. The class can also be used by itself for non-databound access to the database. Of all the ADO .NET classes, the Command class is the closest to the ADO Command class in functionality and remains essen- tially unchanged as far as properties and methods go. Of course, it is a .NET Framework class and does not use COM at all. It also has some enhance- ments over the old ADO Command object. 04Chap.fm Page 79 Monday, November 25, 2002 9:15 PM Comparison of ADO .NET and ADO 2.x 79 DataReader Class The DataReader is used to retrieve data. It is used in conjunction with the Command class to execute an SQL Select statement and then access the returned rows. It provides forward-only read-only access to the data. The DataReader is also used by the DataAdapter to pump data into a DataSet when the Fill method of the DataAdapter is called. The DataReader pro- vides high-speed access to data. You can use a DataReader to pull data for web pages that are read-only, reports, graphs or any other application that does not require data binding and only displays data. The DataAdapter Class The DataAdapter is used to connect DataSets to databases. It is a go-between class. It is comprised of four Command classes and one DataReader class. The DataAdapter is most useful when using data-bound controls in Windows Forms, but it can also be used to provide an easy way to manage the connec- tion between your application and the underlying database tables, views, and stored procedures. Another way of looking at the DataAdapter class is as a way of containing SQL statements and stored procedures for easy program- matic access. All of the SQL needed to maintain a database entity can be con- tained in a DataAdapter object. The DataAdapter also uses support classes that will create the SQL statements for updating the database from a pre- defined Select statement, and will fill the parameter collections of the Command objects contained in the class. There is also a wizard that helps create the DataAdapter and another wizard that will create a DataSet from the Command objects contained within the DataAdapter. COMPARISON OF ADO .NET AND ADO 2.X Since ADO .NET is so different from ADO 2.x (or just ADO), a comparison is a good idea. Those of you who are fluent with ADO will find the transition easier if you have some basis for associating ADO practices with ADO .NET’s. For those of you who have never used ADO, it is still worth the time to see how ADO .NET evolved from ADO and why the changes were made. Here we will look at the differences from a programming point of view. Also, just because ADO .NET is the new kid on the block doesn’t mean that there are not still applications that would be better served by ADO. Each has its strengths and weaknesses. 04Chap.fm Page 80 Monday, November 25, 2002 9:15 PM 80 Chapter 4 • The ADO .NET Class Library Two Different Design Goals ADO and ADO .NET are fundamentally different because the designers had two different goals in mind when they designed the software. ADO is a descendant of the Data Access Objects (DAO)/Remote Data Object (RDO) models. One goal of the designers of ADO was to combine the two older data access technologies into one homogeneous object model that could be used to access any supported database. The other goal was to reduce dependency on open database connectivity (ODBC), an older database standard and replace it with OLEDB, a COM-based standard for connecting to databases. Because of this, the ADO object model was aligned with the two older technologies, DAO and RDO. ADO is also an inherently connected technology. This means that an open database connection is maintained for the life of any of the RecordSet objects that hold data. In later versions of ADO (2.1 and later) it was possible to use a discon- nected architecture. This was added to support stateless web applications. Most desktop applications continued to use the connected model. In some cases this is because the applications needed the concurrency support and were highly transactional. In other cases it was because that was what the programmer knew how to do. ADO .NET was designed to support the stateless model by default. It is an inherently disconnected architecture. While ADO .NET continues to sup- port the OLEDB COM-based database access standard, the new goal is to eliminate even that. ADO .NET uses the new SOAP object protocol and uses XML as its storage and communications medium. The SqlClient classes that support SQL Server are the example of the direction Microsoft is headed. The plan is for developers to create native ADO .NET class libraries to support their database product. The SqlClient classes do not use OLEDB. It is one of the long-term goals of Microsoft to eliminate COM. If it seems to you that they took a 180-degree turn, you are not imagining things. That is part of the reason for this book. The ADO Architecture and Practice With all that said, let’s very quickly review the ADO object model. There are three main objects in ADO. • The Connection object manages database connections and transactions. • The Command object encapsulates SQL statements and manages access to stored procedures. It contains a Parameters collection to manage pass- ing data into and out of stored procedures. 04Chap.fm Page 81 Monday, November 25, 2002 9:15 PM Comparison of ADO .NET and ADO 2.x 81 • The RecordSet object holds the results of SQL queries and implements methods for navigating through the rows and for adding, deleting, and updating rows.
Load more

Recommended publications
  • Chatbot on Serverless/Lamba Architecture Nandan.A Prof.Shilpa Choudary Student, Reva University Professor, Reva University
    SECOND NATIONAL CONFERENCE ON ADVANCES IN COMPUTING AND INFORMATION TECHNOLOGY ISSN:2347-7385 Chatbot on Serverless/Lamba Architecture Nandan.A Prof.Shilpa Choudary Student, Reva University Professor, Reva University Abstract—The OpenLambda, a new, opensource The logic tier contains the code required to translate platform for building next-generation web services user actions at the presentation tier to the and applications on serverless computation. The functionality key aspects of serverless computation and that drives the application’s behavior. The data tier present numerous research challenges that consists of storage media (databases, object stores, must be, addressed in the design and caches, file systems, etc.) that hold the data relevant implementation of such systems. The study of to the application. Figure 1 shows an example of a current web applications, so as to better motivate simple three-tier application. some aspects of serverless application construction. Chatbots platform are used by consumers worldwide for integrating it with backend services . It is still difficult to build and deploy chatbots developers need to handle the coordination of the backend services to build the chatbot interface, integrate the chatbot with external services, and worry about extensibility, scalability, and maintenance. The serverless architecture could be ideal platform to build the chatbot. Figure 1: Architectural pattern for a simple three- tier application Keywords: Lambda Architecture, Chat-bot, Multitier Architecture, Microservices. In Serverless Multi-Tier Architectures a backend remains private and secure. The benefits of this powerful pattern across each tier of a multi-tiered I. INTRODUCTION architecture. Example of a multitiered architecture is The multi-tier application has been a well- a three-tier web application.
    [Show full text]
  • Download Vol 11, No 1&2, Year 2018
    The International Journal on Advances in Internet Technology is published by IARIA. ISSN: 1942-2652 journals site: http://www.iariajournals.org contact: [email protected] Responsibility for the contents rests upon the authors and not upon IARIA, nor on IARIA volunteers, staff, or contractors. IARIA is the owner of the publication and of editorial aspects. IARIA reserves the right to update the content for quality improvements. Abstracting is permitted with credit to the source. Libraries are permitted to photocopy or print, providing the reference is mentioned and that the resulting material is made available at no cost. Reference should mention: International Journal on Advances in Internet Technology, issn 1942-2652 vol. 11, no. 1 & 2, year 2018, http://www.iariajournals.org/internet_technology/ The copyright for each included paper belongs to the authors. Republishing of same material, by authors or persons or organizations, is not allowed. Reprint rights can be granted by IARIA or by the authors, and must include proper reference. Reference to an article in the journal is as follows: <Author list>, “<Article title>” International Journal on Advances in Internet Technology, issn 1942-2652 vol. 11, no. 1 & 2, year 2018, <start page>:<end page> , http://www.iariajournals.org/internet_technology/ IARIA journals are made available for free, proving the appropriate references are made when their content is used. Sponsored by IARIA www.iaria.org Copyright © 2018 IARIA International Journal on Advances in Internet Technology Volume 11, Number 1 & 2, 2018 Editors-in-Chief Mariusz Głąbowski, Poznan University of Technology, Poland Editorial Advisory Board Eugen Borcoci, University "Politehnica"of Bucharest, Romania Lasse Berntzen, University College of Southeast, Norway Michael D.
    [Show full text]
  • Histcoroy Pyright for Online Information and Ordering of This and Other Manning Books, Please Visit Topwicws W.Manning.Com
    www.allitebooks.com HistCoroy pyright For online information and ordering of this and other Manning books, please visit Topwicws w.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact Tutorials Special Sales Department Offers & D e al s Manning Publications Co. 20 Baldwin Road Highligh ts PO Box 761 Shelter Island, NY 11964 Email: [email protected] Settings ©2017 by Manning Publications Co. All rights reserved. Support No part of this publication may be reproduced, stored in a retrieval system, or Sign Out transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid­free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15 percent recycled and processed without the use of elemental chlorine. Manning Publications Co. PO Box 761 Shelter Island, NY 11964 www.allitebooks.com Development editor: Cynthia Kane Review editor: Aleksandar Dragosavljević Technical development editor: Stan Bice Project editors: Kevin Sullivan, David Novak Copyeditor: Sharon Wilkey Proofreader: Melody Dolab Technical proofreader: Doug Warren Typesetter and cover design: Marija Tudor ISBN 9781617292576 Printed in the United States of America 1 2 3 4 5 6 7 8 9 10 – EBM – 22 21 20 19 18 17 www.allitebooks.com HistPoray rt 1.
    [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]
  • Package 'Databaseconnector'
    Package ‘DatabaseConnector’ April 15, 2021 Type Package Title Connecting to Various Database Platforms Version 4.0.2 Date 2021-04-12 Description An R 'DataBase Interface' ('DBI') compatible interface to various database plat- forms ('PostgreSQL', 'Oracle', 'Microsoft SQL Server', 'Amazon Redshift', 'Microsoft Parallel Database Warehouse', 'IBM Netezza', 'Apache Im- pala', 'Google BigQuery', and 'SQLite'). Also includes support for fetching data as 'Andromeda' objects. Uses 'Java Database Connectivity' ('JDBC') to con- nect to databases (except SQLite). SystemRequirements Java version 8 or higher (https://www.java.com/) Depends R (>= 2.10) Imports rJava, SqlRender (>= 1.7.0), methods, stringr, rlang, utils, DBI (>= 1.0.0), urltools, bit64 Suggests aws.s3, R.utils, withr, testthat, DBItest, knitr, rmarkdown, RSQLite, ssh, Andromeda, dplyr License Apache License VignetteBuilder knitr URL https://ohdsi.github.io/DatabaseConnector/, https: //github.com/OHDSI/DatabaseConnector 1 2 R topics documented: BugReports https://github.com/OHDSI/DatabaseConnector/issues Copyright See file COPYRIGHTS RoxygenNote 7.1.1 Encoding UTF-8 R topics documented: connect . .3 createConnectionDetails . .6 createZipFile . .9 DatabaseConnectorDriver . 10 dbAppendTable,DatabaseConnectorConnection,character,data.frame-method . 10 dbClearResult,DatabaseConnectorResult-method . 11 dbColumnInfo,DatabaseConnectorResult-method . 12 dbConnect,DatabaseConnectorDriver-method . 13 dbCreateTable,DatabaseConnectorConnection,character,data.frame-method . 13 dbDisconnect,DatabaseConnectorConnection-method
    [Show full text]
  • Web-Based Content Management System
    Maciej Dobecki, Wojciech Zabierowski / Computing, 2010, Vol. 9, Issue 2, 127-130 [email protected] ISSN 1727-6209 www.computingonline.net International Journal of Computing WEB-BASED CONTENT MANAGEMENT SYSTEM Maciej Dobecki, Wojciech Zabierowski Technical University of Lodz, al. Politechniki 11, 90-924 Łódź, Poland, e-mail: [email protected], [email protected] http://www.dmcs.p.lodz.pl Abstract: This paper describes how to design content management system using the newest web-based techniques. It contains helpful information that can be used during selecting programming language. It introduces multi layer architecture with description and functionality of each layer. It provides description of Model View Controller pattern and how to use it in multi-layer application design. It shows the most powerful Java frameworks that can be applied for each layer and how to connect them in simple way, using Inversion of Control container. It shows power of Spring Framework as business layer, Hibernate as integration layer and ZK Ajax as presentation layer. It proves, that Java combined with applicable libraries can be very powerful tool in good hands. Keywords: CMS, JEE, Spring, Hibernate, AJAX. 1. INTRODUCTION CMS is prepared through a simple-to-use user interface. Usually it is a set of web pages containing The Internet – today is the most powerful and complex forms and modules. popular information media. What was impossible The primary task of the CMS platform is even few years ago is now available by “clicking separation of data content from presentation (the the mouse”. Both small firms and global giants do way of its look).
    [Show full text]
  • MV* Design Patterns
    MV* Design Patterns Alexander Nelson August 30, 2021 University of Arkansas - Department of Computer Science and Computer Engineering Reminders Course Mechanics Course Webpage: https://ahnelson.uark.edu/courses/ csce-4623-mobile-programming-fall-2021/ Syllabus is on the website. Course Communication: https://csce4623-uark.slack.com/ This slack channel is to be the primary mode of communication Projects Choose a project idea and team for the final project ASAP First project report is due September 10th Multitier Architectures What is a multitier architecture? Physical separation of data concerns Examples: • Presentation (UI) • Application Processing • Data Management Why split into layers? OSI Model Why split into layers? Separation of concerns! A change to one layer can have no bearing on the rest of the model e.g. Fiberoptic instead of Coax at the PHY layer OSI Model How does this apply to mobile? Application designers often want separation of UI and logic! Three tier architecture These software engineering abstractions relate to the MV* architectures that are common in mobile computing systems Model View Controller (MVC) Model View Controller 1 1Krasner 1988 Definitions Model: Models are those components of the system application that actually do the work View: Display aspects of the models Controller: Used to send messages to the model, provide interface between model, views, and UI devices. Models Models enable encapsulation Model encapsulates all data as well as methods to change them • Can change the underlying data structures without
    [Show full text]
  • Amazon Aurora Mysql Database Administrator's Handbook
    Amazon Aurora MySQL Database Administrator’s Handbook Connection Management March 2019 Notices Customers are responsible for making their own independent assessment of the information in this document. This document: (a) is for informational purposes only, (b) represents current AWS product offerings and practices, which are subject to change without notice, and (c) does not create any commitments or assurances from AWS and its affiliates, suppliers or licensors. AWS products or services are provided “as is” without warranties, representations, or conditions of any kind, whether express or implied. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. © 2019 Amazon Web Services, Inc. or its affiliates. All rights reserved. Contents Introduction .......................................................................................................................... 1 DNS Endpoints .................................................................................................................... 2 Connection Handling in Aurora MySQL and MySQL ......................................................... 3 Common Misconceptions .................................................................................................... 5 Best Practices ...................................................................................................................... 6 Using Smart Drivers ........................................................................................................
    [Show full text]
  • *Library/ Mentoring/ Association/ Club Activities *Library/ Mentoring
    REGULATION 2020-21 B.Sc. INFORMATION TECHNOLOGY SEMSTER III B.Sc. INFORMATION TECHNOLOGY SL. COMPONENTS HOURS CREDITS PART III CORE SUBJECTS 1. Numerical Method and Operation Research 4 4 2. Object Oriented Programming with C++ 4 4 3. Object Oriented Programming with C++ - LAB 6 3 ALLIED SUBJECTS - 1 4. Data Structure 4 4 5. Data Structure – LAB 4 2 6. Skill Based Core Subject – I DTP 5(IT+4P) 4 7. Non – Major Elective – I 2 2 8. Common Yoga -- 2 TOTAL (5T + 3P = 8 COURSE) 30* 25 *Library/ Mentoring/ Association/ Club Activities SEMSTER IV B.Sc. INFORMATION TECHNOLOGY SL. COMPONENTS HOURS CREDITS PART III CORE SUBJECTS 1. Java Programming 4 4 2. Java Programming Lab 6 3 3. Operating System 4 4 ALLIED SUBJECTS - 1 4. Relational Data Base Management System 4 4 5. ORACLE – LAB 4 2 6. Skill Based Core Subject – II VISUAL PROGRAMMING 5(2T+3P) 4 7. Non – Major Elective – II 2 2 8. Computers for Digital Era -- 2 9. Extension Activity -- 1 10. Library Mentoring and Associations 1 -- TOTAL (5T + 3P = 8 COURSE) 30* 26 *Library/ Mentoring/ Association/ Club Activities SEMSTER V B.Sc. INFORMATION TECHNOLOGY SL. COMPONENTS HOURS CREDITS PART III CORE SUBJECTS 1. Scripting Language 4 4 2. Software Engineering and Testing 4 4 3. Data Communication and Networking 4 4 4. Scripting Language – LAB 6 3 5. Major Elective – I (Group – A) 4 4 Skill Based Common Subject – 6. Personality Development /Effective Communication/Youth 2 2 Leadership 7. Mini Project 5 5 TOTAL (5T + 1P + 1Project = 7 COURSE) 30* 26 *Library/ Mentoring/ Association/ Club Activities SEMSTER VI B.Sc.
    [Show full text]
  • Electronic Commerce Basics
    Electronic Commerce Principles and Practice This Page Intentionally Left Blank Electronic Commerce Principles and Practice Hossein Bidgoli School of Business and Public Administration California State University Bakersfield, California San Diego San Francisco New York Boston London Sydney Tokyo Toronto This book is printed on acid-free paper. ∞ Copyright © 2002 by ACADEMIC PRESS All Rights Reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopy, recording, or any information storage and retrieval system, without permission in writing from the publisher. Requests for permission to make copies of any part of the work should be mailed to: Permissions Department, Harcourt Inc., 6277 Sea Harbor Drive, Orlando, Florida 32887-6777 Academic Press A Harcourt Science and Technology Company 525 B Street, Suite 1900, San Diego, California 92101-4495, USA http://www.academicpress.com Academic Press Harcourt Place, 32 Jamestown Road, London NW1 7BY, UK http://www.academicpress.com Library of Congress Catalog Card Number: 2001089146 International Standard Book Number: 0-12-095977-1 PRINTED IN THE UNITED STATES OF AMERICA 010203040506EB987654321 To so many fine memories of my brother, Mohsen, for his uncompromising belief in the power of education This Page Intentionally Left Blank Contents in Brief Part I Electronic Commerce Basics CHAPTER 1 Getting Started with Electronic Commerce 1 CHAPTER 2 Electronic Commerce Fundamentals 39 CHAPTER 3 Electronic Commerce in Action
    [Show full text]
  • Client Server Communications Middleware Components
    1 Assistant lecturer Ahmed S. Kareem CLIENT SERVER COMMUNICATIONS MIDDLEWARE COMPONENTS The communication middleware software provides the means through which clients and servers communicate to perform specific actions. It also provides specialized services to the client process that insulates the front-end applications programmer from the internal working of the database server and network protocols. In the past, applications programmers had to write code that would directly interface with specific database language (generally a version of SQL) and the specific network protocol used by the database server. Multitier architecture In software engineering, multi-tier architecture (often referred to as n-tier architecture) is a client–server architecture in which the presentation, the application processing, and the data management are logically separate processes. For example, an application that uses middleware to service data requests between a user and a database employs multi-tier architecture. The most widespread use of multi-tier architecture is the three-tier architecture. N-tier application architecture provides a model for developers to create a flexible and reusable application. By breaking up an application into tiers, developers only have to modify or add a specific layer, rather than have to rewrite the entire application over. There should be a presentation tier, a business or data access tier, and a data tier. The concepts of layer and tier are often used interchangeably. However, one fairly common point of view is that there is indeed a difference, and that a layer is a logical structuring mechanism for the elements that make up the software solution, while a tier is a physical structuring mechanism for the system infrastructure.
    [Show full text]
  • Database Language SQL: Integrator of CALS Data Repositories
    Database Language SQL: Integrator of CALS Data Repositories Leonard Gallagher Joan Sullivan U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Information Systems Engineering Division Computer Systems Laboratory Gaithersburg, MD 20899 NIST Database Language SQL Integrator of CALS Data Repositories Leonard Gallagher Joan Sullivan U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Information Systems Engineering Division Computer Systems Laboratory Gaithersburg, MD 20899 September 1992 U.S. DEPARTMENT OF COMMERCE Barbara Hackman Franklin, Secretary TECHNOLOGY ADMINISTRATION Robert M. White, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director Database Language SQL: Integrator of CALS Data Repositories Leonard Gallagher Joan Sullivan National Institute of Standards and Technology Information Systems Engineering Division Gaithersburg, MD 20899, USA CALS Status Report on SQL and RDA - Abstract - The Computer-aided Acquisition and Logistic Support (CALS) program of the U.S. Department of Defense requires a logically integrated database of diverse data, (e.g., documents, graphics, alphanumeric records, complex objects, images, voice, video) stored in geographically separated data banks under the management and control of heterogeneous data management systems. An over-riding requirement is that these various data managers be able to communicate with each other and provide shared access to data and
    [Show full text]