drizzle-kit 1.0.0-beta.4-4605abe → 1.0.0-beta.5-5707f0d
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 +9 -0
- package/api-mysql.mjs +9 -0
- package/api-postgres.d.mts +1619 -1619
- package/api-postgres.d.ts +1619 -1619
- package/api-postgres.js +160 -18
- package/api-postgres.mjs +160 -18
- package/api-sqlite.js +9 -0
- package/api-sqlite.mjs +9 -0
- package/bin.cjs +720 -293
- package/package.json +1 -1
package/api-mysql.js
CHANGED
|
@@ -10676,6 +10676,7 @@ 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();
|
|
10679
10680
|
case `bigint`:
|
|
10680
10681
|
return n6 ? `${value.toString()}n` : value.toString();
|
|
10681
10682
|
case `object`: {
|
|
@@ -19495,6 +19496,14 @@ var init_ddl5 = __esm({
|
|
|
19495
19496
|
columns: "string[]",
|
|
19496
19497
|
nameExplicit: "boolean"
|
|
19497
19498
|
},
|
|
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
|
+
*/
|
|
19498
19507
|
uniques: {
|
|
19499
19508
|
table: "required",
|
|
19500
19509
|
columns: "string[]",
|
package/api-mysql.mjs
CHANGED
|
@@ -10688,6 +10688,7 @@ 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();
|
|
10691
10692
|
case `bigint`:
|
|
10692
10693
|
return n6 ? `${value.toString()}n` : value.toString();
|
|
10693
10694
|
case `object`: {
|
|
@@ -19507,6 +19508,14 @@ var init_ddl5 = __esm({
|
|
|
19507
19508
|
columns: "string[]",
|
|
19508
19509
|
nameExplicit: "boolean"
|
|
19509
19510
|
},
|
|
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
|
+
*/
|
|
19510
19519
|
uniques: {
|
|
19511
19520
|
table: "required",
|
|
19512
19521
|
columns: "string[]",
|