📄 sqlrf.htm
字号:
<!DOCTYPE html public "-//w3c//dtd html 3.2 transitional//en.us"><html lang="en.us"><head><meta name="Generator" content="Quadralay WebWorks Publisher 5.0.4"><meta name="Page" content="DefaultSingle"><meta name="Title" content=" Oracle9i SQL Reference"><title> Oracle9i SQL Reference</title> <link rel="home" href="../../products.htm" title="Library"><link rel="toc" href="toc.htm" title="Contents"><link rel="index" href="index.htm" title="Index"><link rel="copyright" href="../dcommon/html/cpyr.htm" title="Copyright"><link rel="up" href="toc.htm" title="Up"><link rel="next" href="strms.htm" title="Next"><link rel="previous" href="refrn.htm" title="Previous"></head> <body bgcolor="#ffffff"><a name="top"></a><table cellspacing="0" cellpadding="0" width="100%"><tr> <td align="LEFT" valign="TOP"><font color="#330099" face="Helvetica, Arial, sans-serif"><b>Oracle9<i>i</i> Database Generic Documentation Addendum<br>Release 2 (9.2)</b><br>Part Number A97283-01</font></B></td><td valign="BOTTOM" align="RIGHT" width="144"><table cellspacing="0" cellpadding="0" width="50%"><tr><td align="CENTER" valign="TOP" width="25%"><a href="toc.htm"><img src="conticon.gif" alt="Go To Table Of Contents" border="0" height="30"width="30"><br><font size="-2">Contents</font></a></td><td align="CENTER" valign="TOP" width="25%"><a href="index.htm"><img src="indxicon.gif" alt="Go To Index" border="0" height="30"width="30"><br><font size="-2">Index</font></a></td></tr></table></td></tr></table><hr><p><a href="refrn.htm"><img src="larrow.gif" alt="Go to previous page" border="0" height="30" width="40"></a><a href="strms.htm"><img src="rarrow.gif" alt="Go to next page" border="0" height="30" width="40"></a> <div class="IND"><!-- End Header --><a name="1656"></a><!--TOC=Title-"1656"--><h1 class="Title"><font face="Arial, Helvetica, sans-serif" color="#330099">9<br> Oracle9<em class="Italic">i</em> SQL Reference</font></h1><!--/TOC=Title--><a name="1004729"></a><p class="BP">This chapter lists additions and corrections to <em class="Italic">Oracle9i SQL Reference</em>, Release 2 (9.2). </p><a name="1004739"></a><p class="BP">This chapter contains the following topics:</p><ul class="LB1"><li class="LB1" type="DISC"><a name="1004731"></a><a href="sqlrf.htm#1004576">BFILENAME Function</a><p><li class="LB1" type="DISC"><a name="1004732"></a><a href="sqlrf.htm#1004578">Join Query Syntax</a><p><li class="LB1" type="DISC"><a name="1004756"></a><a href="sqlrf.htm#1004581">XML Functions</a><p><li class="LB1" type="DISC"><a name="1004761"></a><a href="sqlrf.htm#1004601">DEBUG Object Privilege</a><p><li class="LB1" type="DISC"><a name="1004766"></a><a href="sqlrf.htm#594142">ALTER TABLE Syntax</a><p><li class="LB1" type="DISC"><a name="1004771"></a><a href="sqlrf.htm#1004740">Setting the Database Time Zone</a><p></ul><a name="1004576"></a><!--TOC=h1-"1004576"--><h2 class="H1"><font face="Arial, Helvetica, sans-serif" color="#330099"> BFILENAME Function</font></h2><!--/TOC=h1--><a name="1004577"></a><p class="BP">When you access <code>BFILE</code> data using the <code>BFILENAME</code> function in any of the Oracle programmatic interfaces, the directory name where the <code>BFILE</code> data exists is case sensitive. That is, you must ensure that you specify the directory object name exactly as it exists in the data dictionary. For example, if an "<code>Admin</code>" directory object was created using mixed case and a quoted identifier in the <code>CREATE</code> <code>DIRECTORY</code> statement, then when using the <code>BFILENAME</code> function in a programmatic interface, you must refer to the directory object as '<code>Admin</code>'.</p><a name="1004578"></a><!--TOC=h1-"1004578"--><h2 class="H1"><font face="Arial, Helvetica, sans-serif" color="#330099"> Join Query Syntax</font></h2><!--/TOC=h1--><a name="1004579"></a><p class="BP">The <em><code>joined_table</code></em> syntax in the <code>SELECT</code> statement incorrectly shows that you can specify <code>CROSS</code> <code>JOIN</code> without a subsequent <em><code>table_reference</code></em>. The correct syntax follows:</p> <pre class="CE"><a name="1004580"></a>{ CROSS JOIN | NATURAL [join_type] JOIN } table_reference</pre> <a name="1004581"></a><!--TOC=h1-"1004581"--><h2 class="H1"><font face="Arial, Helvetica, sans-serif" color="#330099"> XML Functions</font></h2><!--/TOC=h1--><a name="1004582"></a><p class="BP">The documented syntax of some XML built-in functions is incorrect. The correct syntax is shown in the paragraphs that follow, with corrections shown in boldface.</p><a name="1004590"></a><h5 class="SH3"><font face="Arial, Helvetica, sans-serif">EXTRACT (XML)</font></h5><a name="1004662"></a><p class="BP">In the <code>EXTRACT</code> (XML) function, the final optional <em><code>value_expr</code></em> should be <em><code>namespace_string</code></em>, and a comma is required before <em><code>namespace_string</code></em>:</p><a name="1004591"></a><p class="SY"><font face="Arial, Helvetica, sans-serif"><strong class="Bold">extract_xml::=</strong></font></p> <pre class="CE"><a name="1004592"></a>EXTRACT ( XMLType_instance , XPath_string [<strong class="Bold">,</strong> <strong class="Bold">namespace_string</strong> ] )<a name="1004808"></a></pre> <a name="1004688"></a><p class="BP">The optional <em><code>namespace_string</code></em> must resolve to a <code>VARCHAR2</code> value that specifies a default mapping or namespace mapping for prefixes, which Oracle uses when evaluating the XPath expression(s).</p><a name="1004594"></a><h5 class="SH3"><font face="Arial, Helvetica, sans-serif">EXISTSNODE</font></h5><a name="1004663"></a><p class="BP">In the <code>EXISTSNODE</code> function, the final optional <em><code>value_expr</code></em> should be <em><code>namespace_string</code></em> (with the same semantics as described for <code>EXTRACT</code>), and a comma is required before <em><code>namespace_string</code></em>:</p><a name="1004595"></a><p class="SY"><font face="Arial, Helvetica, sans-serif"><strong class="Bold">existsnode::=</strong></font></p> <pre class="CE"><a name="1004596"></a>EXISTSNODE ( XMLType_instance , XPath_string [<strong class="Bold">,</strong> <strong class="Bold">namespace_string</strong> ] )</pre> <a name="1004598"></a><h5 class="SH3"><font face="Arial, Helvetica, sans-serif">EXTRACTVALUE</font></h5><a name="1004664"></a><p class="BP">For consistency with the <code>EXTRACT</code> and <code>EXISTSNODE</code> functions, the final optional argument of the <code>EXTRACTVALUE</code> function is changed from <em><code>value_expr</code></em> to <em><code>namespace_string</code></em>, with the same semantics as described for <code>EXTRACT</code>:</p><a name="1004599"></a><p class="SY"><font face="Arial, Helvetica, sans-serif"><strong class="Bold">extractvalue::=</strong></font></p> <pre class="CE"><a name="1004600"></a>EXTRACTVALUE ( XMLType_instance, XPath_string [, <strong class="Bold">namespace_string</strong>] )</pre> <a name="1004675"></a><h5 class="SH3"><font face="Arial, Helvetica, sans-serif">UPDATEXML</font></h5><a name="1004676"></a><p class="BP">In the <code>UPDATEXML</code> function, the <em><code>Xpath_string</code></em>, <em><code>value_expr</code></em> pair can be repeated, and an optional namespace parameter (with the same semantics as described for <code>EXTRACT</code>) can follow them:</p><a name="1004677"></a><p class="SY"><font face="Arial, Helvetica, sans-serif"><strong class="Bold">updatexml::=</strong></font></p> <pre class="CE"><a name="1004678"></a>UPDATEXML ( XMLType_instance, XPath_string, value_expr<a name="1004679"></a> <strong class="Bold">[, Xpath_string, value_expr ] ... </strong><a name="1004680"></a><strong class="Bold"> [, namespace_string ]</strong> )</pre> <a name="1004653"></a><h5 class="SH3"><font face="Arial, Helvetica, sans-serif">XMLAGG</font></h5><a name="1004665"></a><p class="BP">In the <code>XMLAgg</code> function, the <code>ORDER</code> <code>BY</code> clause is not supported in this release.</p><a name="1004601"></a><!--TOC=h1-"1004601"--><h2 class="H1"><font face="Arial, Helvetica, sans-serif" color="#330099"> DEBUG Object Privilege</font></h2><!--/TOC=h1--><a name="1004602"></a><p class="BP">In this release, you can grant and revoke the <code>DEBUG</code> object privilege (as described in Table 17-3), but Oracle does not yet meaningfully use this privilege. Debugging of PL/SQL and Java routines using the JDWP interface is currently allowed only if the session user has debugging permission on <em class="Italic">all</em> objects, as granted through the <code>DEBUG</code> <code>ANY</code> <code>PROCEDURE</code> system privilege.</p><a name="1004603"></a><p class="BP">The <code>DEBUG</code> <code>ANY</code> <code>PROCEDURE</code> system privilege is currently checked along with the <code>DEBUG</code> <code>CONNECT</code> <code>SESSION</code> system privilege when deciding whether to allow a connection to be established between a database session and a JDWP-based debugger. A connection is not allowed at all unless the user has both of these system privileges.</p><a name="594142"></a><!--TOC=h1-"594142"--><h2 class="H1"><font face="Arial, Helvetica, sans-serif" color="#330099"> ALTER TABLE Syntax</font></h2><!--/TOC=h1--><a name="1004710"></a><p class="BP">In the <code>ALTER</code> <code>TABLE</code> syntax, the <em><code>modify_column_options</code></em> clause has been changed to <em><code>modify_col_properties</code></em>. Some references to this clause in the text were not changed. Any references to <em><code>modify_column_options</code></em> should be read <em><code>modify_col_properties</code></em>.</p><a name="1004713"></a><p class="BP">In addition, the <em><code>modify_col_properties</code></em> clause shows <em><code>modify_LOB_storage_clause</code></em> as a component. This is incorrect. You can specify either <em><code>modify_col_properties</code></em> (without <em><code>modify_LOB_storage_clause</code></em>) or <em><code>modify_LOB_storage_clause</code></em>.</p><a name="1004740"></a><!--TOC=h1-"1004740"--><h2 class="H1"><font face="Arial, Helvetica, sans-serif" color="#330099"> Setting the Database Time Zone</font></h2><!--/TOC=h1--><a name="1004741"></a><p class="BP">Oracle recommends that you set the database time zone (using the <code>CREATE</code> <code>DATABASE</code> or <code>ALTER</code> <code>DATABASE</code> statement) to UTC (0:00). Doing so can improve performance, especially across databases, as no conversion of time zones will be required.</p><!-- Start Footer --></div><div class="OUTD"><hr><table cellspacing="0" cellpadding="0" width="100%"><tr><td valign="BOTTOM" width="33%"><table cellspacing="0" cellpadding="0"><tr><td align="CENTER"><a href="refrn.htm"><img src="larrow.gif" alt="Go to previous page" border="0" height="30" width="40"></a></td><td align="CENTER"><a href="strms.htm"><img src="rarrow.gif" alt="Go to next page" border="0" height="30" width="40"></a></td> </tr></table></td><td align="CENTER" width="34%"><font size="-2">Copyright © 2002 Oracle Corporation.</font><br><font size="-2">All Rights Reserved.</font></td><td valign="BOTTOM" align="RIGHT" width="33%"> <table cellspacing="0" cellpadding="0" width="144"><tr><td align="CENTER" valign="TOP" width="25%"><a href="toc.htm"><img src="conticon.gif" alt="Go To Table Of Contents" border="0" height="30"width="30"><br><font size="-2">Contents</font></a></td><td align="CENTER" valign="TOP" width="25%"><a href="index.htm"><img src="indxicon.gif" alt="Go To Index" border="0" height="30"width="30"><br><font size="-2">Index</font></a></td></tr></table></td></tr></table> </div></body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -