db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r641843 - /db/derby/docs/branches/10.4/src/ref/rreffuncrownumber.dita
Date Thu, 27 Mar 2008 15:19:43 GMT
Author: chaase3
Date: Thu Mar 27 08:19:41 2008
New Revision: 641843

URL: http://svn.apache.org/viewvc?rev=641843&view=rev
Log:
DERBY-3542: New ROW_NUMBER function topic needs a few minor fixes

Made a few small corrections, for consistency and correctness of language.

Modified:
    db/derby/docs/branches/10.4/src/ref/rreffuncrownumber.dita

Modified: db/derby/docs/branches/10.4/src/ref/rreffuncrownumber.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/branches/10.4/src/ref/rreffuncrownumber.dita?rev=641843&r1=641842&r2=641843&view=diff
==============================================================================
--- db/derby/docs/branches/10.4/src/ref/rreffuncrownumber.dita (original)
+++ db/derby/docs/branches/10.4/src/ref/rreffuncrownumber.dita Thu Mar 27 08:19:41 2008
@@ -26,18 +26,18 @@
 </keywords>
 </metadata></prolog>
 <refbody>
-<section> <p>The ROW_NUMBER function does not take any arguments, and for each
row over the window returns an ever increasing BIGINT. It is normally used to limit the number
of rows returned for a query. The LIMIT keyword used in other databases is not defined in
the SQL standard, and is not supported.</p>
-<p>NOTE:<ul>
-<li>Derby does not currently support the named or unnamed window specification to be
specified in the <codeph>OVER()</codeph> clause, but requires an empty parenthesis.
This means the function is evaluated over the entire resultset.</li>
-<li>ROW_NUMBER can currently not be used in a WHERE clause.</li>
-<li>Derby does not currently support ORDER BY in subqueries, meaning there is currently
no guarantee for ordering of rows in the subquery SELECT. An optimizer override can be used
to force the optimizer to use an index ordered on the desired column(s) if ordering is a firm
requirement.</li>
-</ul></p>
+<section> <p>The ROW_NUMBER function does not take any arguments, and for each
row over the window it returns an ever increasing BIGINT. It is normally used to limit the
number of rows returned for a query. The LIMIT keyword used in other databases is not defined
in the SQL standard, and is not supported.</p>
+<ul>
+<li>Derby does not currently allow the named or unnamed window specification to be
specified in the <codeph>OVER()</codeph> clause, but requires an empty parenthesis.
This means the function is evaluated over the entire result set.</li>
+<li>The ROW_NUMBER function cannot currently be used in a WHERE clause.</li>
+<li>Derby does not currently support ORDER BY in subqueries, so there is currently
no way to guarantee the order of rows in the SELECT subquery. An optimizer override can be
used to force the optimizer to use an index ordered on the desired column(s) if ordering is
a firm requirement.</li>
+</ul>
 <p>The data type of the returned value is a BIGINT number.</p> 
 </section>
 
 <refsyn><title>Syntax</title> <codeblock><b>ROW_NUMBER() OVER
()</b></codeblock> </refsyn>
 
-<example><title>Example</title><p>Limiting the number of rows returned
from a query to the 10 first rows of table "T" can be done with the following query:</p>
+<example><title>Example</title><p>To limit the number of rows returned
from a query to the 10 first rows of table <codeph>T</codeph>, use the following
query:</p>
 <codeblock>
 SELECT * FROM (
    SELECT 



Mime
View raw message