@vibeorm/runtime 2.5.0 → 2.6.0

package/dist/index.js

@@ -1306,6 +1306,7 @@ var DATETIME_NEEDS_PRECISION_ASSERTION = Object.freeze({
   mysql: true,
   sqlite: false
 });
+var MILLISECOND_EXACT_NATIVE_TYPE = /^(?:timestamptz|timestamp|datetime)\(\s*[0-3]\s*\)$/i;
 function keysetValidation(params) {
   return new VibeError11({ code: "VIBE_VALIDATION", message: params.message, meta: params.meta });
 }
@@ -1415,9 +1416,9 @@ function compileKeysetOrderPlan(params) {
         meta: { model: model.name, field: field.name, feature: "keysetOrderKey" }
       });
     }
-    if (tag === "t" && DATETIME_NEEDS_PRECISION_ASSERTION[dialect.name] === true && timestampPrecision === undefined) {
+    if (tag === "t" && DATETIME_NEEDS_PRECISION_ASSERTION[dialect.name] === true && timestampPrecision === undefined && (model.isView || !MILLISECOND_EXACT_NATIVE_TYPE.test(field.nativeType ?? ""))) {
       throw keysetUnsupported({
-        message: `keyset pagination cannot order by ${model.name}.${field.name} on ${dialect.name}: this engine may store sub-millisecond timestamps, ` + "and a JavaScript Date truncates them, which would re-deliver rows inside the same millisecond. " + 'Pass keyset: { timestampPrecision: "milliseconds" } to assert the column is millisecond-exact, or order by a lossless key.',
+        message: `keyset pagination cannot order by ${model.name}.${field.name} on ${dialect.name}: this engine may store sub-millisecond timestamps, ` + "and a JavaScript Date truncates them, which would re-deliver rows inside the same millisecond. " + "Declare the column millisecond-exact (@db.Timestamptz(3), dsl.datetime().tz({ precision: 3 })), " + 'pass keyset: { timestampPrecision: "milliseconds" } to assert it is, or order by a lossless key.',
         meta: { model: model.name, field: field.name, feature: "keysetTimestampPrecision", dialect: dialect.name }
       });
     }
@@ -15051,4 +15052,4 @@ export {
   validateWriteData
 };
 
-//# debugId=9B1DF0989FAC48E264756E2164756E21
+//# debugId=F8F07DD9CF6AA47D64756E2164756E21