98 lines
6.4 KiB
HTML
98 lines
6.4 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2005" />
|
||
|
|
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="SQL versus traditional file access terminology" />
|
||
|
|
<meta name="abstract" content="DB2 Universal Database for iSeries provides two access methods for manipulating database tables and data: Structured Query Language (SQL) and system file access methods. They use different words to describe some similar concepts." />
|
||
|
|
<meta name="description" content="DB2 Universal Database for iSeries provides two access methods for manipulating database tables and data: Structured Query Language (SQL) and system file access methods. They use different words to describe some similar concepts." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzatckickoff.htm" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzatcterminology" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>SQL versus traditional file access terminology</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzatcterminology"><a name="rzatcterminology"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">SQL versus traditional file access terminology</h1>
|
||
|
|
<div><p><span class="keyword">DB2 Universal Database™ for iSeries™</span> provides
|
||
|
|
two access methods for manipulating database tables and data: Structured Query
|
||
|
|
Language (SQL) and system file access methods. They use different words to
|
||
|
|
describe some similar concepts.</p>
|
||
|
|
<div class="section"><p>As an interface to <span class="keyword">DB2 Universal Database for iSeries</span>,
|
||
|
|
the <span class="keyword">DB2<sup>®</sup> UDB Query Manager and SQL Development Kit</span> adds
|
||
|
|
an interactive query and report writing interface, as well as precompilers
|
||
|
|
and tools to assist in writing SQL application programs in high-level programming
|
||
|
|
languages. Conforming to the industry standard Structured Query Language (SQL),
|
||
|
|
the SQL implementation for <span class="keyword">i5/OS™</span> allows
|
||
|
|
you to define, manipulate, query, and control access to your <span class="keyword">iSeries</span> data.
|
||
|
|
It works equally well with <span class="keyword">i5/OS</span> files
|
||
|
|
and SQL tables.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">SQL versus traditional file access terminology</h4>
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="50%" id="d0e51">SQL term </th>
|
||
|
|
<th valign="top" width="50%" id="d0e53">Traditional file access term </th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="50%" headers="d0e51 "><img src="./delta.gif" alt="Start of change" /><strong>Collection.</strong> A group of related objects that
|
||
|
|
consists of a library, a journal, a journal receiver, an SQL catalog, and
|
||
|
|
an optional data dictionary. A collection enables the user to find the objects
|
||
|
|
by name.<img src="./deltaend.gif" alt="End of change" /></td>
|
||
|
|
<td valign="top" width="50%" headers="d0e53 "><strong>Library.</strong> A group of related objects that enables
|
||
|
|
the user to find the objects by name.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e51 "><strong>Table.</strong> A set of columns and rows. </td>
|
||
|
|
<td valign="top" width="50%" headers="d0e53 "><strong>Physical file.</strong> A set of records.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e51 "><strong>Row.</strong> The horizontal part of a table containing a serial set
|
||
|
|
of columns. </td>
|
||
|
|
<td valign="top" width="50%" headers="d0e53 "><strong>Record.</strong> A set of fields. </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e51 "><strong>Column.</strong> The vertical part of a table of on data type. </td>
|
||
|
|
<td valign="top" width="50%" headers="d0e53 "><strong>Field.</strong> One of more bytes of related information
|
||
|
|
of one data type.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e51 "><strong>View.</strong> A subset of columns and rows of one or more tables. </td>
|
||
|
|
<td valign="top" width="50%" headers="d0e53 "><strong>Logical file.</strong> A subset of fields or records of
|
||
|
|
up to 32 physical files. </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e51 "><strong>Index.</strong> A collection of data in the columns of a table, logically
|
||
|
|
arranged in ascending or descending order. </td>
|
||
|
|
<td valign="top" width="50%" headers="d0e53 "><strong>Index.</strong> A type of logical file. </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e51 "><strong>Package.</strong> An object that contains control structures for SQL
|
||
|
|
statements to be used by an application server. </td>
|
||
|
|
<td valign="top" width="50%" headers="d0e53 "><strong>SQL package.</strong> An object that contains control
|
||
|
|
structures for SQL statements to be used by an application server. </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e51 "><strong>Catalog.</strong> A set of tables and views that contain information
|
||
|
|
about tables, packages, views, indexes, and constraints. </td>
|
||
|
|
<td valign="top" width="50%" headers="d0e53 ">No similar object. However, the Display File Description
|
||
|
|
(DSPFD) and Display File Field Description (DSPFFD) commands provide some
|
||
|
|
of the same information that querying an SQL catalog provides.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzatckickoff.htm">Database overview</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|