DOCSLIB.ORG

Quick Reference to SQL and SQL*Plus

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Quick Reference to SQL and SQL*Plus APPENDIX A ■ ■ ■ Quick Reference to SQL and SQL*Plus This appendix offers quick references for SQL*Plus and the SQL language. It is far from a com- plete reference, but it should still prove useful. The Oracle documentation contains (besides the comprehensive and complete references) an SQL Quick Reference and a SQL*Plus Quick Reference, but this appendix is much more concise than those two Oracle quick references. You may abbreviate most SQL*Plus commands and their components, as long as you don’t introduce ambiguity. This appendix does not show all SQL*Plus command abbreviation possibilities explicitly, in order to enhance its readability. For example, where this appendix lists the COMPUTE command, it should show it as COMP[UTE], because you can abbreviate the SQL*Plus COMPUTE command to COMP. Abbreviation is available only for SQL*Plus commands; you must always enter SQL commands completely. Refer to SQL*Plus User’s Guide and Reference for all of the abbreviations for SQL*Plus commands and their components. ■Tip When writing SQL*Plus scripts, use the full SQL*Plus commands and the full command component names instead of their abbreviations. This will enhance the readability of your scripts. When you are using SQL*Plus interactively, you may want to use the abbreviations. There are some differences between SQL*Plus and iSQL*Plus; however, this appendix does not list those differences. Refer to SQL*Plus User’s Guide and Reference for more details. The Oracle documentation also explicitly shows all abbreviations for SQL*Plus commands and their components. After a section about the syntax conventions used in this appendix, the commands are organized as follows: • Starting and stopping; entering and executing commands • Working with the SQL*Plus editor, manipulating SQL*Plus scripts, and SQL*Plus inter- activity commands • Variables and parameters • Formatting query results 349 350 APPENDIX A ■ QUICK REFERENCE TO SQL AND SQL*PLUS • SQL: data manipulation (DML), transactions, and queries • SQL: data definition (DDL) • SQL: other commands • SQL: operators, functions, and regular expressions • Rules for naming Oracle database objects; SQL reserved words Note that this appendix also shows constructs, operators, and commands that are not covered in the chapters of this book. Syntax Conventions Used in This Appendix Table A-1 shows the general syntax conventions used in this appendix. Table A-2 identifies the characters and formatting that have special meaning in this appendix. Table A-1. General Syntax Conventions Element Meaning CREATE Command name or keyword, to be entered exactly as spelled (not necessarily in uppercase) str Alphanumeric literal between quotes (string) cond Boolean expression (condition) d, d1, d2 Expressions of datatype DATE expr, e1, e2 Arbitrary expressions m, n Numeric expressions query Query embedded within a command (subquery) txt Alphanumeric expression (with or without quotes) Table A-2. Characters and Formatting with Special Meaning Element Example Meaning [ ] [NOWAIT] Brackets enclose one or more optional items. Options are separated by vertical bars. Underlining [ASC|DESC] Underscored value is the default used if you don’t make a choice yourself. { } {expr1|expr2} Braces enclose two or more items, separated by vertical bars. Choose precisely one of them. ... expr[,...] Horizontal ellipsis indicates that you may repeat the preced- ing item as many times as you like, or that irrelevant parts of the code are omitted. You should not enter the characters of Table A-2 with a special meaning (square brackets, braces, vertical lines, and ellipsis) themselves. Regular parentheses (like the ones surrounding this text), commas, periods, single and double quotation marks (' and "), at signs (@), APPENDIX A ■ QUICK REFERENCE TO SQL AND SQL*PLUS 351 ampersands (&), and any other “exotic” characters have no special meaning in the syntax descriptions in this appendix; therefore, you should enter them verbatim. Starting and Stopping SQLPLUS {-HELP|-VERSION} SQLPLUS [-COMPATIBILITY x.y.z] [/NOLOG|name[/passwd]] [@script] [-MARKUP "options"] [-RESTRICT {1|2|3}] [-SILENT] script ::= {file[.ext]|url} [arg1 arg2 ...]} Start a SQL*Plus session or display help/version information. CONNECT name[/passwd][@database-spec] Create a new SQL*Plus session from the SQL*Plus prompt with the given name/password. DISCONNECT Commit transaction and close database session, but do not exit SQL*Plus. {EXIT|QUIT} [SUCCESS|FAILURE|WARNING|n|var] [COMMIT|ROLLBACK] Close database session and leave SQL*Plus; by default, with a COMMIT and a SUCCESS exit code for the calling environment. PASSWORD [user] Change your password (screen echo suppressed) or change the password for a specific user. SHUTDOWN [ABORT|IMMEDIATE|NORMAL|TRANSACTIONAL [LOCAL]] Shut down the Oracle instance. STARTUP [FORCE] [RESTRICT] [QUIET] [OPEN [READ ONLY]] ... Start up the Oracle instance. There are several additional options for this command. Entering and Executing Commands / Entering a forward slash executes the SQL command in the SQL buffer, without listing the command. DESCRIBE [schema.]obj-name Display the definition/structure of the specified object. Use the SET DESCRIBE command to influence the DESCRIBE command. EXECUTE plsql-statement 352 APPENDIX A ■ QUICK REFERENCE TO SQL AND SQL*PLUS Execute a single PL/SQL statement. HOST [os-command] Execute a single operating system command and return to the SQL*Plus prompt. Without an argument, the HOST command starts a subsession at the operating system level. RUN Display and execute the SQL command in the SQL buffer. TIMING [START txt|SHOW|STOP] Record timing data, list current timer’s name and timing data, or list the number of active timers. Working With the SQL*Plus Editor These commands are not available in iSQL*Plus. Note that this section explicitly shows the SQL*Plus command abbreviations (as opposed to the other sections of this appendix) because these commands are used often. A[PPEND] txt Add txt at the end of the current line in the buffer. Use two spaces to enter a space before txt. C[HANGE] /old[/[new[/]]] Change old on the current line into new. Any nonalphanumeric character is allowed as the separator instead of the slash (/). The third separator is optional; you need it only when new ends with one or more spaces. DEL [n [m]] Delete one or more lines from the buffer. The default is to delete only the current line. Instead of line numbers (n, m), you can also use the following expressions: LAST (last line) or * (current line). I[NPUT] [txt] Add lines to the SQL buffer under the current line. L[IST] [n [m]] Display one or more buffer lines. Without arguments, LIST displays all lines in the buffer. Instead of line numbers, you can use the same special expressions as with the DEL command: * and LAST. APPENDIX A ■ QUICK REFERENCE TO SQL AND SQL*PLUS 353 Manipulating SQL*Plus Scripts Note that most commands listed in this section are not available in iSQL*Plus. EDIT [file[.ext]] Start an external editor and open file.ext. Without an argument, EDIT edits the SQL buffer. GET file[.ext] [LIST|NOLIST] Load the contents of a file into the SQL buffer. REMARK [txt] Enter comments. Oracle ignores txt until the end of the current line. SAVE file[.ext] [CREATE|REPLACE|APPEND] Save the content of the SQL buffer in file.ext. STORE SET file[.ext] [CREATE|REPLACE|APPEND] Save the current SQL*Plus settings in file.ext. {START|@|@@} {url|script[.ext]} [arg1 arg2 ...] Execute script (default file extension SQL). Oracle substitutes arguments for variables &1, &2, and so on. WHENEVER OSERROR {EXIT [SUCCESS|FAILURE|n] [COMMIT|ROLLBACK] |CONTINUE [COMMIT|ROLLBACK|NONE]} Indicate what SQL*Plus should do in case of operating system error conditions. WHENEVER SQLERROR {EXIT [SUCCESS|FAILURE|WARNING|n] [COMMIT|ROLLBACK] |CONTINUE [COMMIT|ROLLBACK|NONE]} Indicate what SQL*Plus should do when SQL commands create error situations. SQL*Plus Interactivity Commands ACCEPT var [NUMBER|CHAR|DATE|BINARY_FLOAT|BINARY_DOUBLE] [FORMAT fmt] [DEFAULT dflt] [PROMPT txt|NOPROMPT] [HIDE] Prompt with txt and assign entered value to variable var. DEFINE [x[=txt]] 354 APPENDIX A ■ QUICK REFERENCE TO SQL AND SQL*PLUS Assign value txt to variable x; show current value for x, or show all defined variables. PAUSE [txt] Display txt (or an empty line) and wait for an Enter keypress. PROMPT [txt] Write txt (or an empty line) to the screen. UNDEFINE x Undefine variable x. Variables and Parameters &n Refer to a command-line parameter in a SQL*Plus script: &1 for the first argument, &2 for the second, and so on. Actually, the ampersand (&) is the default setting for the DEFINE character. See the SQL*Plus SET command. &var, &&var Refer to the value of variable var. If var is undefined, SQL*Plus prompts for a value; with & this happens each time, and with && only once (&& is an implicit DEFINE). A period is the separator between variable names and following text (the CONCAT character). PRINT [var] Display the value of bind variable var, or all current bind variable values. SET sys-var value Assign values to SQL*Plus system variables. The following are common SQL*Plus system variables: APPINFO {ON|OFF|txt] PAGESIZE {14|n} ARRAYSIZE {15|n} PAUSE {ON|OFF|txt} AUTOCOMMIT {ON|OFF|IMMEDIATE|n} RECSEP {WRAPPED|EACH|OFF} AUTOTRACE {ON|OFF|TRACEONLY} [EXPLAIN] RECSEPCHAR { |c} [STATISTICS] CMDSEP {;|c|ON|OFF} SERVEROUTPUT {ON|OFF} [SIZE n] [FORMAT {WRAPPED|WORD_WRAPPED|TRUNC}] COLSEP { |txt} SHOWMODE {ON|OFF} APPENDIX A ■ QUICK REFERENCE TO SQL AND SQL*PLUS 355 CONCAT {.|c|ON|OFF}
Load more

Recommended publications
  • PL/SQL User's Guide and Reference 10G Release 1 (10.1) Part No
    PL/SQL User's Guide and Reference 10g Release 1 (10.1) Part No. B10807-01 December 2003 PL/SQL User's Guide and Reference, 10g Release 1 (10.1) Part No. B10807-01 Copyright © 1996, 2003 Oracle. All rights reserved. Primary Author: John Russell Contributors: Shashaanka Agrawal, Cailein Barclay, Dmitri Bronnikov, Sharon Castledine, Thomas Chang, Ravindra Dani, Chandrasekharan Iyer, Susan Kotsovolos, Neil Le, Warren Li, Bryn Llewellyn, Chris Racicot, Murali Vemulapati, Guhan Viswanathan, Minghui Yang The Programs (which include both the software and documentation) contain proprietary information; 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, except to the extent required to obtain interoperability with other independently created software or as specified by law, 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. This document is not warranted to be 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. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S.
    [Show full text]
  • PL/SQL User's Guide and Reference 10G Release 2 (10.2) B14261-01
    Oracle® Database PL/SQL User's Guide and Reference 10g Release 2 (10.2) B14261-01 June 2005 Oracle Database PL/SQL User’s Guide and Reference 10g Release 2 (10.2) B14261-01 Copyright © 1996, 2005, Oracle. All rights reserved. Contributors: Shashaanka Agrawal, Cailein Barclay, Eric Belden, Dmitri Bronnikov, Sharon Castledine, Thomas Chang, Ravindra Dani, Chandrasekharan Iyer, Susan Kotsovolos, Neil Le, Warren Li, Bryn Llewellyn, Valarie Moore, Chris Racicot, Murali Vemulapati, John Russell, Guhan Viswanathan, Minghui Yang The Programs (which include both the software and documentation) contain proprietary information; 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, except to the extent required to obtain interoperability with other independently created software or as specified by law, 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. This document is not warranted to be 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. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S.
    [Show full text]
  • SQL Engine Reference
    Pervasive.SQL 2000i SQL Engine Reference Reference for Using SQL with Pervasive.SQL 2000 Service Pack 3 Pervasive Software, Inc. 12365 Riata Trace Parkway Building II Austin, TX 78727 USA Telephone: +1 512 231 6000 or 800 287 4383 Fax: +1 512 231 6010 E-Mail: [email protected] Web: http://www.pervasive.com disclaimer PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN “AS IS” BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT. PERVASIVE SOFTWARE INC. MAKES NO OTHER WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THE SOFTWARE OR THE CONTENT OF THE DOCUMENTATION; PERVASIVE SOFTWARE INC. HEREBY EXPRESSLY STATES AND YOU OR YOUR COMPANY ACKNOWLEDGES THAT PERVASIVE SOFTWARE INC. DOES NOT MAKE ANY WARRANTIES, INCLUDING, FOR EXAMPLE, WITH RESPECT TO MERCHANTABILITY, TITLE, OR FITNESS FOR ANY PARTICULAR PURPOSE OR ARISING FROM COURSE OF DEALING OR USAGE OF TRADE, AMONG OTHERS. trademarks Btrieve, Tango, Client/Server in a Box, and the Pervasive Software logo are registered trademarks of Pervasive Software Inc. Built on Pervasive, Built on Pervasive Software, Extranet in a Box, Pervasive.SQL, Jtrieve, Plug n’ Play Databases, SmartScout, Solution Network, Ultra-light Z-DBA, Z-DBA, ZDBA, UltraLight, MicroKernel Database Engine, and MicroKernel Database Architecture are trademarks of Pervasive Software Inc. Microsoft, MS-DOS, Windows, Windows NT, Win32, Win32s, and Visual Basic are registered trademarks of Microsoft Corporation. Windows 95 is a trademark of Microsoft Corporation. NetWare and Novell are registered trademarks of Novell, Inc. NetWare Loadable Module, NLM, Novell DOS, Transaction Tracking System, and TTS are trademarks of Novell, Inc.
    [Show full text]
  • Programmer's Guide to the Oracle Precompilers Release 10.2
    Oracle® Database Programmer’s Guide to the Oracle Precompilers 10g Release 2 (10.2) B14354-01 June 2005 Oracle Database Programmer’s Guide to the Oracle Precompilers, 10g Release 2 (10.2) B14354-01 Copyright © 2001, 2005, Oracle. All rights reserved. Primary Author: Tom Portfolio Contributing Author: Jack Godwin Contributor: Stephen Arnold, Sanford Dreskin, Pierre Dufour, Steve Faris, Radhakrishna Hari, Nancy Ikeda, Ken Jacobs, Maura Joglekar, Phil Locke, Valarie Moore, Lee Osborne, Jacqui Pons, Tim Smith, Gael Turk, Scott Urman, Peter Vasterd The Programs (which include both the software and documentation) contain proprietary information; 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, except to the extent required to obtain interoperability with other independently created software or as specified by law, 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. This document is not warranted to be 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. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S.
    [Show full text]
  • Memo to Users Version 7.4
    IBM i Memo to Users Version 7.4 Memo to Users IBM Note Before using this information and the product it supports, read the information in “Notices” on page 33. This edition applies to version IBM i 7.4 (product number 5770-SS1) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. This document may contain references to Licensed Internal Code. Licensed Internal Code is Machine Code and is licensed to you under the terms of the IBM License Agreement for Machine Code. © Copyright International Business Machines Corporation 1998, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. PDF file for Memorandum to Users.........................................................1 Chapter 2. About IBM i Memo to Users....................................................................3 Who should read this memorandum........................................................................................................... 3 Additional incompatibility information........................................................................................................3 What's new...................................................................................................................................................3 Installing IBM i 7.4 over IBM i 7.2...............................................................................................................4
    [Show full text]
  • Mn/DOT Physical Data Modeling and Implementation Standards
    Mn/DOT Physical Data Modeling And Implementation Standards Mn/DOT Database Administrators Team Version 2.1 Date: August 2011 Mn/DOT Physical Data Modeling and Implementation Standards Version 2.0 Page 1 of 116 Version History Modified By | Date Version Section(s) Comment Approved By Initial Draft taken from Mike’s documentation, useful content 2/11/2010 1.0 found on the Web, and Team additions. Additions made from comments 2/22/2010 1.1 from the 2/11/2009 DBA Team Meeting. Additions made from comments 3/4/2010 1.2 from the 2/22/2010 DBA Team Meeting. Additions made from comments 3/12/2010 1.3 from the 3/11/2010 DBA Team Meeting. Additions made from comments 3/26/2010 1.4 from the 3/25/2010 DBA Team Meeting. 6//2010 1.5 Final Draft Review 6/22/2010 2.0 1st Published Version 8/8/2011 2.1 PL Added Abbreviations/Acronyms 9/23/2011 2.2 PL Added Dimensional Physical Mn/DOT Physical Data Modeling and Implementation Standards Version 2.0 Page 2 of 116 Table of Contents PHYSICAL DATA MODELING STANDARD ................................................................................................................ 6 PURPOSE ........................................................................................................................................................... 6 SCOPE ................................................................................................................................................................ 6 STANDARD .......................................................................................................................................................
    [Show full text]
  • CA Ideal for CA Datacom Programming Guide
    Programming Guide Version 14.02 This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred to as the “Documentation”), is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT.
    [Show full text]
  • PROC SQL: Beyond the Basics Using SAS PROC SQL Beyond the Basics Using SAS® Second Edition ® Lafler
    PROC SQL: Beyond the Basics Using SAS Using Basics the Beyond SQL: PROC PROC SQL Beyond the Basics Using SAS® Second Edition ® Lafler Kirk Paul Lafler From PROC SQL, Second Edition. Full book available for purchase here. Contents About This Book .......................................................................................xv About The Author .................................................................................... xix Acknowledgments ................................................................................... xxi Chapter 1: Designing Database Tables ...................................................... 1 Introduction .................................................................................................................................... 2 Database Design ............................................................................................................................ 2 Conceptual View ...................................................................................................................... 2 Table Definitions ...................................................................................................................... 3 Redundant Information ........................................................................................................... 3 Normalization ........................................................................................................................... 4 Normalization Strategies .......................................................................................................
    [Show full text]
  • PL/SQL User's Guide and Reference
    PL/SQL User’s Guide and Reference Release 2 (9.2) March 2002 Part No. A96624-01 PL/SQL User’s Guide and Reference, Release 2 (9.2) Part No. A96624-01 Copyright © 1996, 2002 Oracle Corporation. All rights reserved. Primary Author: John Russell Contributing Author: Tom Portfolio Contributors: Shashaanka Agrawal, Cailein Barclay, Dmitri Bronnikov, Sharon Castledine, Thomas Chang, Ravindra Dani, Chandrasekharan Iyer, Susan Kotsovolos, Neil Le, Warren Li, Chris Racicot, Murali Vemulapati, Guhan Viswanathan, Minghui Yang 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, except to the extent required to obtain interoperability with other independently created software or as specified by law, 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: Restricted Rights Notice Programs delivered subject to the DOD FAR Supplement are "commercial computer software" and use, duplication, and disclosure of the Programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement.
    [Show full text]
  • Tactics for Pushing SQL to the Relational Databases
    Tactics for Pushing SQL to the Relational Technical Paper Databases December 2008 Tactics for Pushing SQL to Relational Databases Table of Contents Introduction ....................................................................................................................1 Audience for this Paper .............................................................................................1 Purpose of the Paper.................................................................................................1 Scope of This Paper ..................................................................................................1 Overview....................................................................................................................1 Background for This Paper........................................................................................2 Important Concepts ...................................................................................................3 SAS/ACCESS® Software ....................................................................................3 SAS/ACCESS® Interface to ODBC.....................................................................3 SAS/ ACCESS Interface to OLE DB...................................................................3 Databases, Relational Databases, and Relational Database Management Systems (RDBMS) ............................................................................................................................4 Using SAS to Analyze Relational Database Information
    [Show full text]
  • Derby Reference Manual Version 10.15
    Derby Reference Manual Version 10.15 Derby Document build: February 4, 2020, 5:03:53 PM (PST) Version 10.15 Derby Reference Manual Contents Copyright..............................................................................................................................11 License................................................................................................................................. 12 About this guide..................................................................................................................16 Purpose of this document...................................................................................... 16 Audience................................................................................................................... 16 How this guide is organized...................................................................................16 SQL syntax used in this manual............................................................................17 SQL language reference.....................................................................................................18 Capitalization and special characters....................................................................18 SQL identifiers ........................................................................................................ 18 Rules for SQL identifiers..................................................................................... 19 SQLIdentifier.......................................................................................................
    [Show full text]
  • DB2 Server for VSE & VM SQL Reference
    DB2ServerforVSE&VM SQL Reference Version 7 Release 2 SC09-2989-01 DB2ServerforVSE&VM SQL Reference Version 7 Release 2 SC09-2989-01 | Before using this information and the product it supports, be sure to read the general information under “Notices” on page 467. | 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. | Order publications through your IBM representative or the IBM branch office serving your locality or by calling | 1-800-879-2755 in the United States or 1-800-IBM-4YOU in Canada. | When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any | way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1988, 2001. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Summary of Changes ........vii Data Representation Considerations .....29 || Summary of Changes for DB2 Version 7 Release 2 vii Character Conversion ...........29 | Enhancements, New Functions, and New Character Sets and Code Pages .......31 || Capabilities .............vii Coded Character Sets and CCSIDs......31 | Reliability, Availability, and Serviceability Authorization and Privileges ........32 || Improvements............viii Chapter 3. Language Elements ....35 Chapter 1. Introduction ........1 Characters ...............35 Who This Book Is For ...........1 Tokens................36 Prerequisite Knowledge..........1 Spaces...............36 How This Book Is Organized .........1 Comments..............36 Syntax Notation Conventions .........2 Identifiers ...............36 SQL Reserved Words ...........6 SQL Identifiers ............36 Conventions for Representing Mixed Data Values .
    [Show full text]