Oracle Rdb™ SQL Reference Manual Volume 2

Total Page:16

File Type:pdf, Size:1020Kb

Oracle Rdb™ SQL Reference Manual Volume 2 Oracle Rdb™ SQL Reference Manual Volume 2 Release 7.2 for HP OpenVMS Industry Standard 64 for Integrity Servers and OpenVMS Alpha operating systems October 2006 ® DEC_Callout (encoded characters) FullName: DEC Modular Callouts Distiller, PostScript v3011.104 r0 Notice: Copyright 1988 - 1993, Digital Equipment Corporation. Font version: 1.3, 13-Oct-1993 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 40 1.000 41 1.000 42 1.000 43 1.000 44 1.000 45 1.000 46 1.000 47 1.000 50 1.000 51 1.000 52 0.500 53 0.500 54 0.500 55 0.500 56 0.500 57 0.500 cx0 cx1 cx2 cx3 cx4 cx5 cx6 cx7 cx8 cx9 bx0 bx1 bx2 bx3 bx4 bx5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 60 0.500 61 0.500 62 0.500 63 0.500 64 0.375 65 0.375 66 0.375 67 0.375 70 0.375 71 0.375 72 0.375 73 0.375 74 0.375 75 0.375 76 0.500 77 0.500 bx6 bx7 bx8 bx9 mx0 mx1 mx2 mx3 mx4 mx5 mx6 mx7 mx8 mx9 ex0 ex1 2 3 4 5 6 7 8 9 100 0.500 101 0.500 102 0.500 103 0.500 104 0.500 105 0.500 106 0.500 107 0.500 110 0.000 111 0.000 112 0.000 113 0.000 114 0.000 115 0.000 116 0.000 117 0.000 ex2 ex3 ex4 ex5 ex6 ex7 ex8 ex9 120 0.000 121 0.000 122 0.000 123 0.000 124 0.000 125 0.000 126 0.000 127 0.000 130 0.000 131 0.000 132 0.000 133 0.000 134 0.000 135 0.000 136 0.000 137 0.000 140 0.000 141 0.000 142 0.000 143 0.000 144 0.000 145 0.000 146 0.000 147 0.000 150 0.000 151 0.000 152 0.000 153 0.000 154 0.000 155 0.000 156 0.000 157 0.000 160 0.000 161 0.000 162 0.000 163 0.000 164 0.000 165 0.000 166 0.000 167 0.000 170 0.000 171 0.000 172 0.000 173 0.000 174 0.000 175 0.000 176 0.000 177 0.000 0123456789012345678901234567890123456789 240 0.000 241 0.000 242 0.000 243 0.000 244 0.000 245 0.000 246 0.000 247 0.000 250 0.000 251 0.000 252 0.000 253 0.000 254 0.000 255 0.000 256 0.000 257 0.000 260 0.000 261 0.000 262 0.000 263 0.000 264 0.000 265 0.000 266 0.000 267 0.000 270 0.000 271 0.000 272 0.000 273 0.000 274 0.000 275 0.000 276 0.000 277 0.000 300 0.000 301 0.000 302 0.000 303 0.000 304 0.000 305 0.000 306 0.000 307 0.000 310 0.000 311 0.000 312 0.000 313 0.000 314 0.000 315 0.000 316 0.000 317 0.000 320 0.000 321 0.000 322 0.000 323 0.000 324 0.000 325 0.000 326 0.000 327 0.000 330 0.000 331 0.000 332 0.000 333 0.000 334 0.000 335 0.000 336 0.000 337 0.000 340 0.000 341 0.000 342 0.000 343 0.000 344 0.000 345 0.000 346 0.000 347 0.000 350 0.000 351 0.000 352 0.000 353 0.000 354 0.000 355 0.000 356 0.000 357 0.000 360 0.000 361 0.000 362 0.000 363 0.000 364 0.000 365 0.000 366 0.000 367 0.000 370 0.000 371 0.000 372 0.000 373 0.000 374 0.000 375 0.000 376 0.000 377 0.000 SQL Reference Manual, Volume 2 Oracle Rdb Release 7.2 for HP OpenVMS Industry Standard 64 for Integrity Servers and OpenVMS Alpha operating systems Copyright © 1987, 2006 Oracle Corporation. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the programs is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation. If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are ‘‘commercial computer software’’ or ‘‘commercial technical data’’ pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee’s responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle Corporation disclaims liability for any damages caused by such use of the Programs. Oracle is a registered trademark, and Oracle Rdb, Hot Standby, LogMiner for Rdb, Oracle CODASYL DBMS, Oracle RMU, Oracle CDD/Repository, Oracle SQL/Services, Oracle Trace, and Rdb are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services, or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Contents Send Us Your Comments ........................................... vii Preface ........................................................... ix 6 SQL Statements ACCEPT Statement ......................................... 6–2 ALTER Statements ......................................... 6–7 ALTER CONSTRAINT Statement .............................. 6–8 ALTER DATABASE Statement ................................ 6–12 ALTER DOMAIN Statement . ................................. 6–86 ALTER FUNCTION Statement ................................ 6–102 ALTER INDEX Statement . ................................. 6–109 ALTER MODULE Statement . ................................. 6–131 ALTER OUTLINE Statement ................................. 6–138 ALTER PROCEDURE Statement .............................. 6–144 ALTER PROFILE Statement . ................................. 6–150 ALTER ROLE Statement ..................................... 6–152 ALTER SEQUENCE Statement ................................ 6–155 ALTER STORAGE MAP Statement ............................. 6–164 ALTER SYNONYM Statement ................................. 6–179 ALTER TABLE Statement . ................................. 6–181 ALTER TRIGGER Statement . ................................. 6–221 ALTER USER Statement ..................................... 6–224 ALTER VIEW Statement ..................................... 6–227 ATTACH Statement ......................................... 6–233 BEGIN DECLARE Statement ................................. 6–244 CALL Statement for Simple Statements ......................... 6–247 CALL Statement for Compound Statements ...................... 6–250 iii CASE (Searched) Control Statement ............................ 6–254 CASE (Simple) Control Statement .............................. 6–256 CLOSE Statement .......................................... 6–259 COMMENT ON Statement ................................... 6–261 COMMIT Statement . ...................................... 6–269 Compound Statement . ...................................... 6–275 CONNECT Statement . ...................................... 6–290 CREATE Statements . ...................................... 6–302 CREATE CACHE Clause ..................................... 6–303 CREATE CATALOG Statement . .............................. 6–314 CREATE COLLATING SEQUENCE Statement .................... 6–318 CREATE DATABASE Statement . .............................. 6–323 CREATE DOMAIN Statement . .............................. 6–386 CREATE FUNCTION Statement . .............................. 6–399 CREATE INDEX Statement ................................... 6–400 CREATE MODULE Statement . .............................. 6–426 CREATE OUTLINE Statement . .............................. 6–451 CREATE PROCEDURE Statement ............................. 6–474 CREATE PROFILE Statement . .............................. 6–475 CREATE ROLE Statement ................................... 6–478 CREATE ROUTINE Statement . .............................. 6–483 CREATE SCHEMA Statement . .............................. 6–503 Index Tables 6–1 Updating Data Definitions While Users Are Attached to the Database .............................................. 6–64 6–2 Updating Database-Wide Parameters While Users Are Attached to the Database ........................................... 6–68 6–3 Constraint Attributes Syntax Permutations and Equivalents . ..... 6–190 6–4 ALTER and DROP Statements Causing or Not Causing Stored Routine Invalidation ..................................... 6–434 iv Send Us Your Comments Oracle Rdb for OpenVMS Oracle SQL Reference Manual, Release 7.2 Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this publication. Your input is an important part of the information used for revision. • Did you find any errors? • Is the information clearly presented? • Do you need more information? If so, where? • Are the examples correct? Do you need more examples? • What features did you like most? If you find any errors or have any other suggestions for improvement, please indicate the document title, chapter, section, and page number (if available).
Recommended publications
  • Database Application Development Overview SQL in Application Code SQL in Application Code (Contd.) Embedded SQL Embedded SQL: Va
    Overview Concepts covered in this lecture: Database Application Development SQL in application code Embedded SQL Cursors Chapter 6 Dynamic SQL JDBC SQLJ Stored procedures Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 2 SQL in Application Code SQL in Application Code (Contd.) SQL commands can be called from within a host language (e.g., C++ or Java) program. Impedance mismatch: SQL statements can refer to host variables SQL relations are (multi-) sets of records, with (including special variables used to return status). no a priori bound on the number of records. Must include a statement to connect to the right No such data structure exist traditionally in database. procedural programming languages such as Two main integration approaches: C++. (Though now: STL) Embed SQL in the host language (Embedded SQL, SQL supports a mechanism called a cursor to SQLJ) handle this. Create special API to call SQL commands (JDBC) Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 3 Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 4 Embedded SQL Embedded SQL: Variables Approach: Embed SQL in the host language. A preprocessor converts the SQL statements into special API calls. EXEC SQL BEGIN DECLARE SECTION Then a regular compiler is used to compile the char c_sname[20]; code. long c_sid; short c_rating; float c_age; Language constructs: EXEC SQL END DECLARE SECTION Connecting to a database: EXEC SQL CONNECT Declaring variables: Two special “error” variables: EXEC SQL BEGIN (END) DECLARE SECTION SQLCODE (long, is negative if an error has occurred) Statements: SQLSTATE (char[6], predefined codes for common errors) EXEC SQL Statement; Database Management Systems 3ed, R.
    [Show full text]
  • Openvms Guide
    Mimer SQL OpenVMS Guide Version 11.0 Mimer SQL, OpenVMS Guide, Version 11.0, January 2018 © Copyright Mimer Information Technology AB. The contents of this manual may be printed in limited quantities for use at a Mimer SQL installation site. No parts of the manual may be reproduced for sale to a third party. Information in this document is subject to change without notice. All registered names, product names and trademarks of other companies mentioned in this documentation are used for identification purposes only and are acknowledged as the property of the respective company. Companies, names and data used in examples herein are fictitious unless otherwise noted. Produced and published by Mimer Information Technology AB, Uppsala, Sweden. Mimer SQL Web Sites: https://developer.mimer.com https://www.mimer.com Contents i Contents .............................................................................................................................. i Chapter 1 Introduction .......................................................................................1 About Mimer SQL for OpenVMS...................................................................................1 The Mimer SQL Database Server .................................................................................. 1 Embedded SQL................................................................................................................. 1 Module SQL......................................................................................................................
    [Show full text]
  • Embedded SQL N Functions and Procedural Constructs N Triggers
    CS425 – Summer 2016 Jason Arnold Chapter 6: Advanced SQL modified from: Database System Concepts, 6th Ed. ©Silberschatz, Korth and Sudarshan See www.db-book.com for conditions on re-use Chapter 6: Advanced SQL n Accessing SQL From a Programming Language l Dynamic SQL JDBC and ODBC l Embedded SQL n Functions and Procedural Constructs n Triggers Textbook: Chapter 5 CS425 – Fall 2013 – Boris Glavic 5.2 ©Silberschatz, Korth and Sudarshan Accessing SQL From a Programming Language CS425 – Fall 2013 – Boris Glavic 5.3 ©Silberschatz, Korth and Sudarshan JDBC and ODBC n API (application-program interface) for a program to interact with a database server n Application makes calls to l Connect with the database server l Send SQL commands to the database server l Fetch tuples of result one-by-one into program variables n ODBC (Open Database Connectivity) works with C, C++, C#, and Visual Basic l Other API’s such as ADO.NET sit on top of ODBC n JDBC (Java Database Connectivity) works with Java CS425 – Fall 2013 – Boris Glavic 5.4 ©Silberschatz, Korth and Sudarshan Native APIs n Most DBMS also define DBMS specific APIs n Oracle: OCI n Postgres: libpg … CS425 – Fall 2013 – Boris Glavic 5.5 ©Silberschatz, Korth and Sudarshan JDBC n JDBC is a Java API for communicating with database systems supporting SQL. n JDBC supports a variety of features for querying and updating data, and for retrieving query results. n JDBC also supports metadata retrieval, such as querying about relations present in the database and the names and types of relation attributes.
    [Show full text]
  • Developing Embedded SQL Applications
    IBM DB2 10.1 for Linux, UNIX, and Windows Developing Embedded SQL Applications SC27-3874-00 IBM DB2 10.1 for Linux, UNIX, and Windows Developing Embedded SQL Applications SC27-3874-00 Note Before using this information and the product it supports, read the general information under Appendix B, “Notices,” on page 209. Edition Notice This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such. You can order IBM publications online or through your local IBM representative. v To order publications online, go to the IBM Publications Center at http://www.ibm.com/shop/publications/ order v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at http://www.ibm.com/ planetwide/ To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU (426-4968). When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corporation 1993, 2012. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Introduction to embedded Include files for COBOL embedded SQL SQL................1 applications .............29 Embedding SQL statements
    [Show full text]
  • SQL in Application Programs JDBC: Java Database Connectivity
    SQL in Application Programs JDBC: Java Database Connectivity CLI: Call-Level Interface Embedded SQL We have seen how SQL is used at the generic query interface --- an environment where we sit at a terminal and ask queries of a database. Reality is almost always different: conventional programs interacting with SQL. Want to consider: How do we enable a database to interact with an “ordinary” program written in a language such as C or Java? How do we deal with the differences in data types supported by SQL and conventional languages? In particular, relations, which are the result of queries, are not directly supported by conventional languages. A common environment for using a database has three tiers of processors: 1. Web servers --- Connect users to the database, usually over the Internet, or possibly a local connection. 2. Application servers --- Execute the “business logic” – whatever it is the system is supposed to do. 3. Database servers --- Run the DBMS and execute queries and modifications at the request of the application servers. Database holds the information about products, customers, etc. Business logic includes things like “what do I do after someone clicks ‘checkout’?” Answer: Show the “How will you pay for this?” screen. For this section, we will deal with the interaction between the application and the DBMS A SQP environment is the framework under which data exists and SQL operations are executed. Think of a SQL environment as a DBMS running at some installation. So tables, triggers, views, etc are defined within a SQL environment Database servers maintain some number of connections, so app servers can ask queries or perform modifications.
    [Show full text]
  • Embedded SQL Guide for RM/Cobol
    Firebird Embedded SQL Guide for RM/Cobol Embedded SQL Guide for RM/Cobol 3 Table of Contents 1. Program Structure...............................................................................................................................6 1.1. General...........................................................................................................................................6 1.2. Reading this Guide.........................................................................................................................6 1.3. Definition of Terms........................................................................................................................6 1.4. Declaring Host Variables...............................................................................................................7 1.5. Declaring and Accessing Databases...............................................................................................7 1.6. Transactions....................................................................................................................................7 1.7. SQL Statements..............................................................................................................................8 1.8. Statement Handles..........................................................................................................................8 1.9. Dynamic SQL (DSQL)...................................................................................................................8 1.10. Error
    [Show full text]
  • Free Pascal Sql Select with Like Clause
    Free Pascal Sql Select With Like Clause Spiritualistic Claude usually overtoils some urolith or crews devotionally. Bartholemy obliterate sinisterly while unrestored Charley fubbed languorously or expertizes flatteringly. Unreproaching and thermogenetic Ignatius still denounced his hoaxer ravingly. Many machines as such features including zmbufdataset unit, to assign the line options manipulation capabilities of the address to perform different component with pascal, binary collating sequence is very reason Test runner that allows DUnit Tests to output NUnit compatible XML. Connection to the DB could smuggle the grade is those Tables and Fields actually there, supporting joint development efforts, profile parameters of the SAP system etc. Bug cannot remove hook up to ensure that the firebird allows you use the database location of leonardos upcoming posts and free pascal sql select with like clause too big table to follow this may know about! If you include a Column now, so the comma comes after the eight column name, fit better still use one house the Free Pascal mirror sites. You can freeze anything that want shut it. In the TextBox control type echo following SQL statement. ZONE which also stores the time zone. The same order by the column definitions, like sql with free pascal select clause. The databases reverential integrity will make tough very difficult. Delphi ide plugin for this blog and database file, which extend this with free pascal sql select with like clause to be. How to define future new exception type. The leave that visitors are registered is such order anymore the SQL is called and hunger find not the most reliable is compulsory register them in each order of launch, window, at least.
    [Show full text]
  • Database Programming Week 9
    Database Programming Week 9 *Some of the slides in this lecture are created by Prof. Ian Horrocks from University of Oxford SQL in Real Programs • We have seen only how SQL is used at the generic query interface --- an environment where we sit at a terminal and ask queries of a database. • Reality is almost always different. – Programs in a conventional language like C are written to access a database by “calls” to SQL statements. 2 Database Programming Code in Programming Language SQL Sequence of tuples Database 3 SQL in Application Code • SQL commands can be called from within a host language (e.g., C++ or Java) program. – SQL statements can refer to host variables (including special variables used to return status). – Must include a statement to connect to the right database. • Two main integration approaches: – Embed SQL in the host language (embedded SQL, SQLJ) – Create special API to call SQL commands (JDBC) 4 SQL in Application Code (Con’t) • Impedance mismatch – SQL relations are (multi-) sets of records, with no a priori bound on the number of records. Typically, no such data structure in programming languages such as C/ C++ (Though now: STL). – SQL supports a mechanism called a cursor to handle this. 5 Embedded SQL • Approach: Embed SQL in the host language. – A preprocessor converts/translates the SQL statements into special API calls. – Then a regular compiler is used to compile the code. 6 Embedded SQL • Language constructs: – Connecting to a database !EXEC SQL CONNECT :usr_pwd;! !// the host variable usr_pwd contains your
    [Show full text]
  • Openvms Guide
    Mimer SQL OpenVMS Guide Version 10.1 Mimer SQL, OpenVMS Guide, Version 10.1, December 2017 © Copyright Mimer Information Technology AB. The contents of this manual may be printed in limited quantities for use at a Mimer SQL installation site. No parts of the manual may be reproduced for sale to a third party. Information in this document is subject to change without notice. All registered names, product names and trademarks of other companies mentioned in this documentation are used for identification purposes only and are acknowledged as the property of the respective company. Companies, names and data used in examples herein are fictitious unless otherwise noted. Produced and published by Mimer Information Technology AB, Uppsala, Sweden. P.O. Box 1713, SE-751 47 Uppsala, Sweden. Tel +46(0)18-780 92 00. Fax +46(0)18-780 92 40. Mimer SQL Web Sites: http://developer.mimer.com http://www.mimer.com Contents i Contents .............................................................................................................................. i Chapter 1 Introduction ....................................................................................... 1 About Mimer SQL for OpenVMS...................................................................................1 The Mimer SQL Database Server .................................................................................. 1 Embedded SQL................................................................................................................. 1 JDBC Driver......................................................................................................................
    [Show full text]
  • Embedded SQL Call-Level Interface Java Database Connectivity
    Real SQL Programming Embedded SQL Call-Level Interface Java Database Connectivity 1 SQL in Real Programs We have seen only how SQL is used at the generic query interface --- an environment where we sit at a terminal and ask queries of a database. Reality is almost always different. Programs in a conventional language like C are written to access a database by “calls” to SQL statements. 2 Host Languages Any conventional language can be a host language, that is, a language in which SQL calls are embedded. The use of a host/SQL combination allows us to do anything computable, yet still get the very-high-level SQL interface to the database. 3 Connecting SQL to the Host Language 1. Embedded SQL is a standard for combining SQL with seven languages. 2. CLI (Call-Level Interface ) is a different approach to connecting C to an SQL database. 3. JDBC (Java Database Connectivity ) is a way to connect Java with an SQL database. 4 Embedded SQL Key idea: Use a preprocessor to turn SQL statements into procedure calls that fit with the host-language code surrounding. All embedded SQL statements begin with EXEC SQL, so the preprocessor can find them easily. 5 Shared Variables To connect SQL and the host-language program, the two parts must share some variables. Declarations of shared variables are bracketed by: EXEC SQL BEGIN DECLARE SECTION; Always needed <host-language declarations> EXEC SQL END DECLARE SECTION; 6 Use of Shared Variables In SQL, the shared variables must be preceded by a colon. They may be used as constants provided by the host-language program.
    [Show full text]
  • Mimer SQL on Openvms Present and Future
    Mimer SQL on OpenVMS Present and Future Bengt Gunne, CTO 1 Agenda . Background . Mimer customers . Platforms . Technical features . Mimer SQL on OpenVMS . Ongoing development . Q&A 2 Bengt Gunne . Started working with Mimer in 1981 – Have worked with many parts of the system such as: . Database kernel . Transaction handling . Client/server communications . Clients such as ODBC and ADO.NET . Overall design . Multiuser systems for PDP, VMS, HP-UX, Windows etc. Most recently written a new SQL optimizer – Head of development since 1991 – Chief Technical Officer 3 Who was Mimer? Mimer was a giant in the Norse Mythology who guarded the well of wisdom. The gods came to Mimer for advice. When they looked into the well they could see everything that happened in the world. The god Oden even took out one of his eyes and put it in the well to be able to see everything at all times. Today, ordinary people come to Mimer for advice… 4 Mimer Information Technology AB . HQ in Uppsala, Sweden – Office in Stockholm and Beijing – Partners in China, Japan, Korea, Central Europe, and USA . World class experts in relational database technology . Developer of the Mimer SQL product family – Enterprise Solutions – Industrial/Automotive/Embedded Solutions – Mobile Solutions . Mimer SQL used in mission critical systems world wide since the 1970s 5 What is Mimer SQL? . Relational database management system . Standard SQL . Runs on many platforms – Tight integration with OpenVMS 6 Company focus . The company focuses solely on Mimer SQL – Tools are through third party integrations . How is this possible/facilitated? – Standard SQL – Standard programming interfaces Requires a truly open system 7 Mimer SQL background .
    [Show full text]
  • Embedded SQL in Java
    SQLJ: Embedded SQL in Java This chapter introduces SQLJ, a relatively new standard that many database vendors have already adopted. SQLJ differs from JDBC in that SQL statements can be embedded directly in Java programs and translation-time semantics checks can be performed. It is a powerful tool that complements JDBC access to databases. Programming in SQLJ is discussed in detail in this chapter, and an application program for the investment portfolio database is presented. 6.1 What Is SQLJ? SQLJ is an emerging database programming tool that allows embedding of static SQL statements in Java programs, very much like Pro*C or Pro*C++. SQLJ is an attractive alternative to JDBC because it allows translation-time syntax and semantics checking of static SQL statements. As a consequence, application programs developed in SQLJ are more robust. SQLJ’s syntax is also much more compact than that of JDBC, resulting in shorter programs and increased user productivity. The SQLJ translator converts Java programs embedded with static SQL state- ments into pure Java code, which can then be executed through a JDBC driver against the database. Programmers can also perform dynamic SQL access to the database using JDBC features. 273 274 SQLJ: Embedded SQL in Java 6.2 Simple Example A simple program in SQLJ is presented in this section. This program illustrates the essential steps that are needed to write an SQLJ program. These steps follow: 1. Import necessary classes.In addition to the JDBC classes, java.sql.*, every SQLJ program will need to include the SQLJ run-time classes sqlj.runtime.* and sqlj.runtime.ref.*.
    [Show full text]