Documentation.

h2/src/docsrc/help/help.csv

@@ -3372,6 +3372,7 @@ To get the row number after ordering and grouping, use a subquery.
 ","
 SELECT ROWNUM(), * FROM TEST;
 SELECT ROWNUM(), * FROM (SELECT * FROM TEST ORDER BY NAME);
+SELECT ID FROM (SELECT T.*, ROWNUM AS R FROM TEST T) WHERE R BETWEEN 2 AND 3;
 "
 
 "Functions (System)","SCHEMA","

h2/src/docsrc/html/jaqu.html

@@ -64,13 +64,17 @@ auto-complete in the IDE and Javadoc and are supported. Type checking is perform
 JaQu fully protects against SQL injection.
 </p>
 <p>
-JaQu is much smaller than persistence frameworks such as Hibernate.
+JaQu is more a replacement for JDBC than it is a replacement for tools like Hibernate.
+With JaQu, you don't write SQL statements as Strings.
+JaQu is much smaller and simpler than other persistence frameworks such as Hibernate,
+but it also does not provide all the features of those.
 Unlike iBatis and Hibernate, no XML or annotation based configuration is required;
 instead the configuration (if required at all) is done in pure Java, in the application itself.
 </p>
 <p>
 JaQu does not require or contain any data caching mechanism. Like JDBC and iBatis,
-JaQu provides full control over when and what SQL statements are executed.
+JaQu provides full control over when and what SQL statements are executed
+(but without having to write SQL statements as Strings).
 </p>
 
 <h3>Restrictions</h3>

h2/src/docsrc/html/performance.html

@@ -127,7 +127,7 @@ It will be hard for the developers of Derby to improve the performance to a reas
 A few problems have been identified: leaving autocommit on is a problem for Derby.
 If it is switched off during the whole test, the results are about 20% better for Derby.
 Derby does not call FileDescriptor.sync() or FileChannel.force(..) on each commit.
-Derby supports a testing mode (system property <code>derby.system.durability=test</code>) 
+Derby supports a testing mode (system property <code>derby.system.durability=test</code>)
 where durability is disabled. According to the documentation, this setting should be used for testing only,
 as the database may not recover after a crash. Enabling this setting improves performance
 by a factor of 2.6 (embedded mode) or 1.4 (server mode). Even if enabled, Derby is still less

h2/src/docsrc/html/tutorial.html

@@ -188,7 +188,7 @@ by clicking on the message.
 
 <h3>Adding Database Drivers</h3>
 <p>
-Additional database drivers to connect to other databases (MySQL, PostgreSQL, HSQLDB,...) 
+Additional database drivers to connect to other databases (MySQL, PostgreSQL, HSQLDB,...)
 can be registered by adding the Jar file location of the driver to the environment
 variables <code>H2DRIVERS</code> or <code>CLASSPATH</code>.
 Example (Windows): to add the database driver library