Javadoc regenerated

Author: fluentfuture

apidocs/com/google/mu/safesql/SafeSql.html

@@ -1477,7 +1477,8 @@ <h3>paginateLazily</h3>
  <a href="https://docs.oracle.com/en/java/javase/24/docs/api/java.base/java/lang/Class.html" title="class or interface in java.lang" class="external-link">Class</a>&lt;? extends T&gt;&nbsp;resultType)</span></div>
 <div class="block">Paginate the encapsulated query by fetching up to <code>pageSize</code> rows for each page.
 
- <p>If <code>orderByKeys</code> is non-empty, the column values are used to control pagination.
+ <p>If <code>orderByKeys</code> is non-empty, they refer to the columns that must uniquely identify
+ a row. These column values are then used to control pagination.
  For example, if <code>[groupId, timestamp]</code> can uniquely identify a row, the generated
  SQL will use <code>"groupId" &gt; ? OR ("groupId" = ? AND "timestamp" &gt; ?)</code> for the next page,
  comparing against the previous page's last row.
@@ -1488,10 +1489,11 @@ <h3>paginateLazily</h3>
 
  <p>The standard SQL <code>FETCH NEXT ROWS</code> syntax is used for pagination.
  If <code>orderByKeys</code> is empty, the paginated query will use <code>OFFSET</code> keyword
- to specify the next page offset.
+ instead of the sort key columns to specify the next page offset.
 
- <p>All column names are automatically double-quoted to avoid clashing with keywords or spaces
- in identifiers. If your DB is case sensitive, make sure you pass in the accurate case.
+ <p>The <code>orderByKeys</code> column names are automatically double-quoted to avoid clashing
+ with keywords or spaces in identifiers. 
+ If your DB is case sensitive, make sure you pass in the accurate case.
 
  <p>The method is lazy. Paginated queries are only sent when the returned stream is consumed.
  The caller should close the <code>connection</code> after done, which will close the cached
@@ -1523,7 +1525,8 @@ <h3>paginateLazily</h3>
  <a href="https://docs.oracle.com/en/java/javase/24/docs/api/java.base/java/lang/Class.html" title="class or interface in java.lang" class="external-link">Class</a>&lt;? extends T&gt;&nbsp;resultType)</span></div>
 <div class="block">Paginate the encapsulated query by fetching up to <code>pageSize</code> rows for each page.
 
- <p>If <code>orderByKeys</code> is non-empty, the column values are used to control pagination.
+ <p>If <code>orderByKeys</code> is non-empty, they refer to the columns that must uniquely identify
+ a row. These column values are then used to control pagination.
  For example, if <code>[groupId, timestamp]</code> can uniquely identify a row, the generated
  SQL will use <code>"groupId" &gt; ? OR ("groupId" = ? AND "timestamp" &gt; ?)</code> for the next page,
  comparing against the previous page's last row.
@@ -1534,10 +1537,11 @@ <h3>paginateLazily</h3>
 
  <p>The standard SQL <code>FETCH NEXT ROWS</code> syntax is used for pagination.
  If <code>orderByKeys</code> is empty, the paginated query will use <code>OFFSET</code> keyword
- to specify the next page offset.
+ instead of the sort key columns to specify the next page offset.
 
- <p>All column names are automatically double-quoted to avoid clashing with keywords or spaces
- in identifiers. If your DB is case sensitive, make sure you pass in the accurate case.
+ <p>The <code>orderByKeys</code> column names are automatically double-quoted to avoid clashing
+ with keywords or spaces in identifiers. 
+ If your DB is case sensitive, make sure you pass in the accurate case.
 
  <p>The method is lazy. Paginated queries are only sent when the returned stream is consumed.
  The caller should close the <code>connection</code> after done, which will close the cached
@@ -1569,7 +1573,8 @@ <h3>paginateLazily</h3>
  <a href="SqlFunction.html" title="interface in com.google.mu.safesql">SqlFunction</a>&lt;? super <a href="https://docs.oracle.com/en/java/javase/24/docs/api/java.sql/java/sql/ResultSet.html" title="class or interface in java.sql" class="external-link">ResultSet</a>, ? extends T&gt;&nbsp;rowMapper)</span></div>
 <div class="block">Paginate the encapsulated query by fetching up to <code>pageSize</code> rows for each page.
 
- <p>If <code>orderByKeys</code> is non-empty, the column values are used to control pagination.
+ <p>If <code>orderByKeys</code> is non-empty, they refer to the columns that must uniquely identify
+ a row. These column values are then used to control pagination.
  For example, if <code>[groupId, timestamp]</code> can uniquely identify a row, the generated
  SQL will use <code>"groupId" &gt; ? OR ("groupId" = ? AND "timestamp" &gt; ?)</code> for the next page,
  comparing against the previous page's last row.
@@ -1580,10 +1585,11 @@ <h3>paginateLazily</h3>
 
  <p>The standard SQL <code>FETCH NEXT ROWS</code> syntax is used for pagination.
  If <code>orderByKeys</code> is empty, the paginated query will use <code>OFFSET</code> keyword
- to specify the next page offset.
+ instead of the sort key columns to specify the next page offset.
 
- <p>All column names are automatically double-quoted to avoid clashing with keywords or spaces
- in identifiers. If your DB is case sensitive, make sure you pass in the accurate case.
+ <p>The <code>orderByKeys</code> column names are automatically double-quoted to avoid clashing
+ with keywords or spaces in identifiers. 
+ If your DB is case sensitive, make sure you pass in the accurate case.
 
  <p>The method is lazy. Paginated queries are only sent when the returned stream is consumed.
  The caller should close the <code>connection</code> after done, which will close the cached
@@ -1615,7 +1621,8 @@ <h3>paginateLazily</h3>
  <a href="SqlFunction.html" title="interface in com.google.mu.safesql">SqlFunction</a>&lt;? super <a href="https://docs.oracle.com/en/java/javase/24/docs/api/java.sql/java/sql/ResultSet.html" title="class or interface in java.sql" class="external-link">ResultSet</a>, ? extends T&gt;&nbsp;rowMapper)</span></div>
 <div class="block">Paginate the encapsulated query by fetching up to <code>pageSize</code> rows for each page.
 
- <p>If <code>orderByKeys</code> is non-empty, the column values are used to control pagination.
+ <p>If <code>orderByKeys</code> is non-empty, they refer to the columns that must uniquely identify
+ a row. These column values are then used to control pagination.
  For example, if <code>[groupId, timestamp]</code> can uniquely identify a row, the generated
  SQL will use <code>"groupId" &gt; ? OR ("groupId" = ? AND "timestamp" &gt; ?)</code> for the next page,
  comparing against the previous page's last row.
@@ -1626,10 +1633,11 @@ <h3>paginateLazily</h3>
 
  <p>The standard SQL <code>FETCH NEXT ROWS</code> syntax is used for pagination.
  If <code>orderByKeys</code> is empty, the paginated query will use <code>OFFSET</code> keyword
- to specify the next page offset.
+ instead of the sort key columns to specify the next page offset.
 
- <p>All column names are automatically double-quoted to avoid clashing with keywords or spaces
- in identifiers. If your DB is case sensitive, make sure you pass in the accurate case.
+ <p>The <code>orderByKeys</code> column names are automatically double-quoted to avoid clashing
+ with keywords or spaces in identifiers. 
+ If your DB is case sensitive, make sure you pass in the accurate case.
 
  <p>The method is lazy. Paginated queries are only sent when the returned stream is consumed.
  The caller should close the <code>connection</code> after done, which will close the cached