60 lines
4.7 KiB
HTML
60 lines
4.7 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="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="concept" />
|
||
|
|
<meta name="DC.Title" content="Process special data types" />
|
||
|
|
<meta name="abstract" content="Most data types, such as INTEGER and CHARACTER, do not have any special processing characteristics. However, there are a few data types that require special functions or locators in order to use them." />
|
||
|
|
<meta name="description" content="Most data types, such as INTEGER and CHARACTER, do not have any special processing characteristics. However, there are a few data types that require special functions or locators in order to use them." />
|
||
|
|
<meta name="DC.subject" content="object-relational, definition, application domain and object-orientation" />
|
||
|
|
<meta name="keywords" content="object-relational, definition, application domain and object-orientation" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafykickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafylobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafyuddt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafyexampcomplex.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafydatalinks.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbafyusoocap" />
|
||
|
|
<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>Process special data types</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafyusoocap"><a name="rbafyusoocap"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Process special data types</h1>
|
||
|
|
<div><p>Most data types, such as INTEGER and CHARACTER, do not have any
|
||
|
|
special processing characteristics. However, there are a few data types that
|
||
|
|
require special functions or locators in order to use them.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafylobs.htm">Use large objects (LOBs)</a></strong><br />
|
||
|
|
The VARCHAR, VARGRAPHIC, and VARBINARY data types have a limit of 32 KB (where KB equals 1024 bytes) of storage. While this may be sufficient for small to medium-size text data, applications often need to store large text documents. They might also need to store a wide variety of additional data types such as audio, video, drawings, mixed text and graphics, and images. There are three data types to store these data objects as strings of up to 2 GB (where GB equals 1 073 741 824 bytes).</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafyuddt.htm">Use user-defined distinct types (UDT)</a></strong><br />
|
||
|
|
A user-defined distinct type is a mechanism that allows you to
|
||
|
|
extend DB2<sup>®</sup> capabilities
|
||
|
|
beyond the built-in data types available.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafyexampcomplex.htm">Examples of using UDTs, UDFs, and LOBs</a></strong><br />
|
||
|
|
The following examples show how you can use user-defined types (UDTs), user-defined functions (UDFs), and large objects (LOBs) together in complex applications.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbafydatalinks.htm">Use DataLinks</a></strong><br />
|
||
|
|
The DataLink data type is one of the basic building blocks for extending the types of data that can be stored in database files. The idea of a DataLink is that the actual data stored in the column is only a pointer to the object.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafykickoff.htm" title="These topics describe the iSeries server implementation of the Structured Query Language (SQL) using DB2 UDB for iSeries and the DB2 UDB Query Manager and SQL Development Kit Version 5 licensed program.">SQL programming</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|