@prisma-next/cli 0.1.0-dev.22 → 0.1.0-dev.24

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/dist/cli.js CHANGED
@@ -1411,6 +1411,9 @@ function createDbInitCommand() {
1411
1411
  };
1412
1412
  return dbInitResult2;
1413
1413
  }
1414
+ if (!flags.quiet && flags.json !== "object") {
1415
+ console.log("Applying migration plan and verifying schema...");
1416
+ }
1414
1417
  const callbacks = {
1415
1418
  onOperationStart: (op) => {
1416
1419
  if (!flags.quiet && flags.json !== "object") {
@@ -1420,20 +1423,22 @@ function createDbInitCommand() {
1420
1423
  onOperationComplete: (_op) => {
1421
1424
  }
1422
1425
  };
1423
- const runnerResult = await withSpinner(
1424
- () => runner.execute({
1425
- plan: migrationPlan,
1426
- driver,
1427
- destinationContract: contractIR,
1428
- policy,
1429
- callbacks,
1430
- frameworkComponents
1431
- }),
1432
- {
1433
- message: "Applying migration plan...",
1434
- flags
1435
- }
1436
- );
1426
+ const runnerResult = await runner.execute({
1427
+ plan: migrationPlan,
1428
+ driver,
1429
+ destinationContract: contractIR,
1430
+ policy,
1431
+ callbacks,
1432
+ // db init plans and applies back-to-back from a fresh introspection, so per-operation
1433
+ // pre/postchecks and the idempotency probe are usually redundant overhead. We still
1434
+ // enforce marker/origin compatibility and a full schema verification after apply.
1435
+ executionChecks: {
1436
+ prechecks: false,
1437
+ postchecks: false,
1438
+ idempotencyChecks: false
1439
+ },
1440
+ frameworkComponents
1441
+ });
1437
1442
  if (!runnerResult.ok) {
1438
1443
  throw errorRuntime(runnerResult.failure.summary, {
1439
1444
  why: runnerResult.failure.why ?? `Migration runner failed: ${runnerResult.failure.code}`,