drizzle-kit 1.0.0-beta.4-03f09f7 → 1.0.0-beta.4-332ec7b

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/api-mysql.js CHANGED
@@ -10676,7 +10676,6 @@ var init_stringify = __esm({
10676
10676
  case `number`:
10677
10677
  return Number.isFinite(value) ? value.toString() : `null`;
10678
10678
  case `boolean`:
10679
- return value.toString();
10680
10679
  case `bigint`:
10681
10680
  return n6 ? `${value.toString()}n` : value.toString();
10682
10681
  case `object`: {
@@ -19496,14 +19495,6 @@ var init_ddl5 = __esm({
19496
19495
  columns: "string[]",
19497
19496
  nameExplicit: "boolean"
19498
19497
  },
19499
- /**
19500
- * Unique constraints and unique indexes are functionally identical in terms of behavior
19501
- * We decided to keep both constraints and indexes because when a unique constraint is created
19502
- * it cannot be removed, whereas an index can be dropped
19503
- * Removing unique constraints would require recreating the table
19504
- * Before the beta v1 all unique constraints were created and stored in snapshots as indexes
19505
- * We do not have sufficient information for upping snapshots to beta v1
19506
- */
19507
19498
  uniques: {
19508
19499
  table: "required",
19509
19500
  columns: "string[]",
package/api-mysql.mjs CHANGED
@@ -10688,7 +10688,6 @@ var init_stringify = __esm({
10688
10688
  case `number`:
10689
10689
  return Number.isFinite(value) ? value.toString() : `null`;
10690
10690
  case `boolean`:
10691
- return value.toString();
10692
10691
  case `bigint`:
10693
10692
  return n6 ? `${value.toString()}n` : value.toString();
10694
10693
  case `object`: {
@@ -19508,14 +19507,6 @@ var init_ddl5 = __esm({
19508
19507
  columns: "string[]",
19509
19508
  nameExplicit: "boolean"
19510
19509
  },
19511
- /**
19512
- * Unique constraints and unique indexes are functionally identical in terms of behavior
19513
- * We decided to keep both constraints and indexes because when a unique constraint is created
19514
- * it cannot be removed, whereas an index can be dropped
19515
- * Removing unique constraints would require recreating the table
19516
- * Before the beta v1 all unique constraints were created and stored in snapshots as indexes
19517
- * We do not have sufficient information for upping snapshots to beta v1
19518
- */
19519
19510
  uniques: {
19520
19511
  table: "required",
19521
19512
  columns: "string[]",