example in paginateLazily() javadoc

Author: fluentfuture

mug-safesql/src/main/java/com/google/mu/safesql/SafeSql.java

@@ -989,13 +989,13 @@ public <T> Optional<T> queryForOne(
    *
    * <p>If {@code orderByKeys} 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]} can uniquely identify a row, the generated
-   * SQL will use {@code "groupId" > ? OR ("groupId" = ? AND "timestamp" > ?)} for the next page,
+   * For example, if {@code [timestamp, saleId]} can uniquely identify a row, the generated
+   * SQL will use {@code "timestamp" > ? OR ("timestamp" = ? AND "saleId" > ?)} for the next page,
    * comparing against the previous page's last row.
    * 
-   * <p>You can also use descending order, for example by passing {@code "NAME DESC"}.
-   * The generated paginated query will then use {@code "NAME" < ?} instead of {@code "NAME > ?}
-   * for the next page. 
+   * <p>You can also use descending order, for example by passing {@code "Timestamp DESC"}.
+   * The generated paginated query will then use {@code "timestamp" < ?} instead of
+   * {@code "timestamp" > ?} for the next page. 
    * 
    * <p>The standard SQL {@code FETCH NEXT ROWS} syntax is used for pagination.
    * If {@code orderByKeys} is empty, the paginated query will use {@code OFFSET} keyword
@@ -1030,13 +1030,13 @@ public <T> Stream<List<T>> paginateLazily(
    *
    * <p>If {@code orderByKeys} 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]} can uniquely identify a row, the generated
-   * SQL will use {@code "groupId" > ? OR ("groupId" = ? AND "timestamp" > ?)} for the next page,
+   * For example, if {@code [timestamp, saleId]} can uniquely identify a row, the generated
+   * SQL will use {@code "timestamp" > ? OR ("timestamp" = ? AND "saleId" > ?)} for the next page,
    * comparing against the previous page's last row.
    * 
-   * <p>You can also use descending order, for example by passing {@code "NAME DESC"}.
-   * The generated paginated query will then use {@code "NAME" < ?} instead of {@code "NAME > ?}
-   * for the next page. 
+   * <p>You can also use descending order, for example by passing {@code "Timestamp DESC"}.
+   * The generated paginated query will then use {@code "timestamp" < ?} instead of
+   * {@code "timestamp" > ?} for the next page. 
    * 
    * <p>The standard SQL {@code FETCH NEXT ROWS} syntax is used for pagination.
    * If {@code orderByKeys} is empty, the paginated query will use {@code OFFSET} keyword
@@ -1074,13 +1074,13 @@ public <T> Stream<List<T>> paginateLazily(
    *
    * <p>If {@code orderByKeys} 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]} can uniquely identify a row, the generated
-   * SQL will use {@code "groupId" > ? OR ("groupId" = ? AND "timestamp" > ?)} for the next page,
+   * For example, if {@code [timestamp, saleId]} can uniquely identify a row, the generated
+   * SQL will use {@code "timestamp" > ? OR ("timestamp" = ? AND "saleId" > ?)} for the next page,
    * comparing against the previous page's last row.
    * 
-   * <p>You can also use descending order, for example by passing {@code "NAME DESC"}.
-   * The generated paginated query will then use {@code "NAME" < ?} instead of {@code "NAME > ?}
-   * for the next page. 
+   * <p>You can also use descending order, for example by passing {@code "Timestamp DESC"}.
+   * The generated paginated query will then use {@code "timestamp" < ?} instead of
+   * {@code "timestamp" > ?} for the next page. 
    * 
    * <p>The standard SQL {@code FETCH NEXT ROWS} syntax is used for pagination.
    * If {@code orderByKeys} is empty, the paginated query will use {@code OFFSET} keyword
@@ -1115,13 +1115,13 @@ public <T> Stream<List<T>> paginateLazily(
    *
    * <p>If {@code orderByKeys} 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]} can uniquely identify a row, the generated
-   * SQL will use {@code "groupId" > ? OR ("groupId" = ? AND "timestamp" > ?)} for the next page,
+   * For example, if {@code [timestamp, saleId]} can uniquely identify a row, the generated
+   * SQL will use {@code "timestamp" > ? OR ("timestamp" = ? AND "saleId" > ?)} for the next page,
    * comparing against the previous page's last row.
    * 
-   * <p>You can also use descending order, for example by passing {@code "NAME DESC"}.
-   * The generated paginated query will then use {@code "NAME" < ?} instead of {@code "NAME > ?}
-   * for the next page. 
+   * <p>You can also use descending order, for example by passing {@code "Timestamp DESC"}.
+   * The generated paginated query will then use {@code "timestamp" < ?} instead of
+   * {@code "timestamp" > ?} for the next page. 
    * 
    * <p>The standard SQL {@code FETCH NEXT ROWS} syntax is used for pagination.
    * If {@code orderByKeys} is empty, the paginated query will use {@code OFFSET} keyword