@xenon-device-management/xenon 2.16.0 → 2.17.1

package/lib/src/scripts/initialize-database.js

@@ -30,18 +30,12 @@ const run_migrations_1 = require("./run-migrations");
  * prisma/schema.prisma's provider to `databaseProvider`. With `postgresql`,
  * that left a PostgreSQL schema in the checkout that the SQLite file couldn't
  * use.
- *
- * It first warns of changes to prisma/schema.prisma that no migration makes.
- * `npm run db:generate` gives the developer's database a migration history, and
- * from then on it is updated with `migrate deploy`, which never applies them,
- * while the log said the schema was in sync.
  */
 function main() {
     return __awaiter(this, void 0, void 0, function* () {
         // A PostgreSQL URL would otherwise reach the history read and fail there,
         // under a message about the file.
         (0, database_check_1.assertSupportedDatabase)();
-        (0, run_migrations_1.warnOfUnmigratedSchemaChanges)();
         yield (0, run_migrations_1.syncDatabaseSchema)();
         logger_1.default.info('[DBInit] Generating Prisma Client...');
         (0, node_child_process_1.execSync)('npx prisma generate', {