@rebasepro/server-mongo 0.14.1-canary.g7e666eb → 0.14.1

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@rebasepro/server-mongo",
   "type": "module",
-  "version": "0.14.1-canary.g7e666eb",
+  "version": "0.14.1",
   "description": "MongoDB backend for Rebase",
   "funding": {
     "url": "https://github.com/sponsors/rebaseco"
@@ -40,9 +40,9 @@
   "dependencies": {
     "mongodb": "^7.5.0",
     "ws": "^8.21.1",
-    "@rebasepro/common": "0.14.1-canary.g7e666eb",
-    "@rebasepro/types": "0.14.1-canary.g7e666eb",
-    "@rebasepro/utils": "0.14.1-canary.g7e666eb"
+    "@rebasepro/common": "0.14.1",
+    "@rebasepro/types": "0.14.1",
+    "@rebasepro/utils": "0.14.1"
   },
   "devDependencies": {
     "@types/jest": "^30.0.0",
@@ -55,7 +55,7 @@
     "vite": "^8.1.5"
   },
   "peerDependencies": {
-    "@rebasepro/server": "0.14.1-canary.g7e666eb"
+    "@rebasepro/server": "0.14.1"
   },
   "peerDependenciesMeta": {
     "@rebasepro/server": {

package/src/db/MongoConditionBuilder.ts

@@ -292,6 +292,18 @@ export class MongoConditionBuilder {
         return this.combineConditionsWithAnd(conditions) ?? {};
     }
 
+    /**
+     * The primary key's name in a stored document.
+     *
+     * Rows leave this driver with `_id` renamed to `id` — see
+     * `MongoDataService.documentToRow` — so `id` is the only name a caller ever
+     * sees, and the one the SDK's own examples use for a tie-breaker. A sort
+     * document naming `id` names a field no document has: Mongo does not
+     * complain, it just returns them in natural order, so `.orderBy("id")` read
+     * as "no sort at all" with a 200 to go with it.
+     */
+    private static readonly ID_FIELD = "_id";
+
     /**
      * Build MongoDB sort options from Rebase options
      *
@@ -299,6 +311,15 @@ export class MongoConditionBuilder {
      * a multi-key sort is expressed directly: the keys are applied in insertion
      * order, each breaking ties on the one before it.
      *
+     * The id closes every sort, descending, for the same reason the Postgres
+     * driver appends `id DESC`: it is what makes the ordering *total*. Without
+     * it, two rows sharing a sort value are returned in whatever order the
+     * engine pleases, and that order is free to differ between two executions of
+     * the same query — so paging by `offset` over a non-unique sort column
+     * repeats some rows and skips others. A single-column sort has always had
+     * this exposure here; a multi-key sort merely made it easier to reach, since
+     * the whole point of the later keys is that the earlier ones tie.
+     *
      * @param orderBy - Field to order by, or the `[field, direction]` list
      * @param order - Sort direction, for the single-field spelling
      * @returns MongoDB sort object
@@ -314,7 +335,13 @@ export class MongoConditionBuilder {
         // would sort by, and letting a later duplicate overwrite it would order
         // by a direction the caller listed as less significant.
         for (const [field, direction] of keys) {
-            if (!(field in sort)) sort[field] = direction === "desc" ? -1 : 1;
+            const key = field === "id" ? MongoConditionBuilder.ID_FIELD : field;
+            if (!(key in sort)) sort[key] = direction === "desc" ? -1 : 1;
+        }
+        // Already named by the caller — at whatever direction and rank they
+        // chose — the sort is total and there is nothing left to break.
+        if (!(MongoConditionBuilder.ID_FIELD in sort)) {
+            sort[MongoConditionBuilder.ID_FIELD] = -1;
         }
         return sort;
     }