bun-query-builder 0.2.50 → 0.2.52

package/dist/migrations.d.ts

@@ -49,7 +49,7 @@ export declare function canonicalStorageType(col: ColumnPlan, dialect: Supported
  * differently by a live DB vs a model (quoting, casts, `now()` vs
  * `CURRENT_TIMESTAMP`, `0` vs `'0'`) compare equal.
  */
-export declare function canonicalizeDefault(col: ColumnPlan): string | undefined;
+export declare function canonicalizeDefault(col: ColumnPlan, dialect?: SupportedDialect): string | undefined;
 /**
  * Generate comprehensive SQL to migrate from a previous plan to a new plan,
  * plus a structured list of the operations involved (so callers can gate
@@ -83,6 +83,24 @@ export declare function generateDiffSql(previous: MigrationPlan | undefined, nex
  * are recorded, run once, and never removed.
  */
 export declare const GENERATED_MARKER: '-- qb:generated';
+/**
+ * The database's own clock, in UTC, as a default.
+ *
+ * A managed `created_at` used to default to `CURRENT_TIMESTAMP`, which is the
+ * *session's local* wall clock on both Postgres and MySQL. On a host set to
+ * anything but UTC that writes digits that never happened in UTC, and every
+ * reader is out by the offset - it surfaced in ReviewOS as "7 hours ago" on a
+ * row written seconds earlier. The column type is not the bug and is unchanged:
+ * naive UTC is the convention, because MySQL has nothing equivalent to
+ * `timestamptz`.
+ *
+ * This is the marker, not the SQL. Each driver renders it in its own spelling,
+ * because there is no portable one: Postgres wants `(now() AT TIME ZONE 'utc')`,
+ * MySQL takes `UTC_TIMESTAMP` only inside brackets, and SQLite's
+ * `CURRENT_TIMESTAMP` is already UTC and is the only dialect that was right by
+ * accident.
+ */
+export declare const UTC_CLOCK_DEFAULT: 'UTC_TIMESTAMP';
 export declare interface ColumnPlan {
   name: string
   type: NormalizedColumnType