74 lines
4.4 KiB
HTML
74 lines
4.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="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="SQLTables Description" />
|
||
|
|
<meta name="abstract" content="The following is a discussion about SQLTables description." />
|
||
|
|
<meta name="description" content="The following is a discussion about SQLTables description." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikodbcapifunctions.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="sqltablesdesc" />
|
||
|
|
<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>SQLTables Description</title>
|
||
|
|
</head>
|
||
|
|
<body id="sqltablesdesc"><a name="sqltablesdesc"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">SQLTables Description</h1>
|
||
|
|
<div><p>The following is a discussion about SQLTables description.</p>
|
||
|
|
<div class="section"><ul><li>The CatalogName parameter is ignored, with or without wildcards, since
|
||
|
|
the catalog name is always the relational database name. The only time the
|
||
|
|
catalog name value matters is when it must be an empty string to generate
|
||
|
|
a list of libraries for the server. <p>You must specify table names for
|
||
|
|
the TableName parameter exactly as you would when creating a SQL statement.
|
||
|
|
In other words, you must capitalize the table name unless you created the
|
||
|
|
table name with double quotes around the table name. If you created the table
|
||
|
|
with double quotes around the table name, you need to specify the TableName
|
||
|
|
parameter as it appears in quotes, matching the case of the letters.</p>
|
||
|
|
</li>
|
||
|
|
<li>The "Library view" option on the <strong>Catalog</strong> tab of the DSN setup GUI
|
||
|
|
only affects this API when you choose the combination that attempts to retrieve
|
||
|
|
the list of libraries for that server. It does not allow you to generate
|
||
|
|
a result set based on a search through multiple libraries for specific tables.</li>
|
||
|
|
<li>The "Object description type" option on the <strong>Catalog</strong> tab of the
|
||
|
|
DSN setup GUI affects the output you get in the "RESULTS" column of the result
|
||
|
|
set when getting a list of tables.</li>
|
||
|
|
<li>If you have a string with mixed '\_' and '_' then if SQL_ATTR_METADATA_ID
|
||
|
|
is SQL_FALSE then we'll treat the first '\_' as an actual '_', but the '_'
|
||
|
|
will be treated as the wildcard. If SQL_ATTR_METADATA_ID is SQL_TRUE then
|
||
|
|
the first '\_' will be treated like an actual '_' and the '_' will also be
|
||
|
|
treated like an actual '_'. The driver will internally convert the second
|
||
|
|
'_' to a '\_'.</li>
|
||
|
|
<li>In order to use the wildcard character underscore (_) as a literal precede
|
||
|
|
it with a backlash (\). For example, to search for only MY_TABLE (not MYATABLE,
|
||
|
|
MYBTABLE, etc...) you need to specify the search string as MY\_TABLE. <p>Specifiying
|
||
|
|
'\%' in a name is invalid, as the iSeries™ server does not allow an actual
|
||
|
|
'%' in a library or table name.</p>
|
||
|
|
<p>When queried for the list of libraries,
|
||
|
|
the driver returns the TABLE_CAT and REMARKS fields as meaningful data. </p>
|
||
|
|
<p>The
|
||
|
|
ODBC specification says to return everything, except the TABLE_SCHEM as nulls.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaikodbcapifunctions.htm" title="Learn about implementations issues when using ODBC APIs.">Implementation issues of ODBC APIs</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|