@voltro/database 0.42.0 → 0.43.1

package/dist/sql.d.ts

@@ -817,7 +817,7 @@ export declare interface ColumnSnapshot {
      * never reached the comparison. So the differ was not comparing lengths wrongly
      * — it could not see them. Adding `.maxLength(n)` to an EXISTING column planned
      * zero operations and reported "schema is up to date" while the live column
-     * stayed `longtext`. A consumer hit that trying to apply the documented remedy
+     * stayed `longtext`. A deployment hit that trying to apply the documented remedy
      * for MariaDB's hash long-unique, and their contrast is what pinned it: a column
      * bounded AT CREATION was `varchar(64)` (DDL path, fine), one bounded afterwards
      * stayed `longtext` (diff path, blind).
@@ -2408,7 +2408,7 @@ export declare const reactiveTriggerName: (tableName: string, channel: string) =
  * dimension at all, so `db plan` reports 0 operations and `db apply` reports
  * "schema is up to date" while the drift detector is simultaneously telling
  * you 500 tables have no trigger, and pointing at `voltro db apply` as the
- * remedy. Reported by a consumer with 525 tables and 27 triggers, all 27 on
+ * remedy. Reported from a real deployment with 525 tables and 27 triggers, all 27 on
  * framework tables.
  *
  * A single instance is unaffected — its own writes reach its own subscribers