New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: Check command is not working on drizzle-kit@0.21.0 #2284
Comments
same here
|
Looking into it, thanks! |
+1, ran into the same issue. |
Got this issue aswell on 0.21.2. Following the stack trace, this seems to come from what I assume to be a dev test forgotten where it ignores the desired dialect from config/params and instead runs all three dialects. Code snipped pulled from var checkCommand = new import_commander.Command("check").option("--config <config>", `Drizzle config file path`).option("--dialect <dialect>", "Database dialect").option("--out <out>", `Output folder`).action(async (options) => {
await printVersions();
await assertOrmCoreVersion();
const params = cliConfigCheck.parse(options);
const { out, dialect: dialect7 } = await assertOutFolder(params);
checkHandler(out, "postgresql");
checkHandler(out, "sqlite");
checkHandler(out, "mysql");
console.log("Everything's fine \u{1F436}\u{1F525}");
});
var upCommand = new import_commander.Command("up").option("--config <config>", `Drizzle config file path`).option("--dialect <dialect>", "Database dialect").option("--out <out>", `Output folder`).action(async (options) => {
await printVersions();
await assertOrmCoreVersion();
const params = cliConfigCheck.parse(options);
const { out, dialect: dialect7 } = await assertOutFolder(params);
await assertPackages("drizzle-orm");
if (dialect7 === "postgresql") {
upPgHandler(out);
}
if (dialect7 === "mysql") {
upMysqlHandler(out);
}
if (dialect7 === "sqlite") {
upSqliteHandler(out);
}
}); @AndriiSherman Might be useful information if you're still looking into this :) |
+1 here! |
having the same issue, upgraded from
To
here is my drizzle.config.ts if it help
|
same problem here |
+1, ran into the same issue. Versions |
Same here
|
Here is a patch (for pnpm) diff --git a/bin.cjs b/bin.cjs
index 02a2165a023b86ad1bbc2e3fef1193404b2c97f1..787b7830b3f6d88b19c916e2eed34d1b9b1ceeba 100644
--- a/bin.cjs
+++ b/bin.cjs
@@ -113659,9 +113659,7 @@ var checkCommand = new import_commander.Command("check").option("--config <confi
await assertOrmCoreVersion();
const params = cliConfigCheck.parse(options);
const { out, dialect: dialect7 } = await assertOutFolder(params);
- checkHandler(out, "postgresql");
- checkHandler(out, "sqlite");
- checkHandler(out, "mysql");
+ checkHandler(out, dialect7);
console.log("Everything's fine \u{1F436}\u{1F525}");
});
var upCommand = new import_commander.Command("up").option("--config <config>", `Drizzle config file path`).option("--dialect <dialect>", "Database dialect").option("--out <out>", `Output folder`).action(async (options) => {
|
This should be fixed in |
lifesaver, thanks |
What version of
drizzle-orm
are you using?0.30.10
What version of
drizzle-kit
are you using?0.21.0
Describe the Bug
When I updated
drizzle-kit
to the new version (0.21.0), the check command stopped working. The first time, the response was as follows:So I ran the
drizzle-kit up
command and got the following return:After that, I expected it to work, but that's not the case. Executing the check command after all these procedures, the command returns the following error:
Expected behavior
No response
Environment & setup
The text was updated successfully, but these errors were encountered: