You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using MySQL, I get a panic on sqlc generate. I've added some debug logs to narrow down the migration/statement causing the issue, and it's from an ETL step, which is in our migrations but doesn't need to be considered by sqlc:
UPDATE x INNER JOIN y ON y.a = x.a SET x.b = y.b;
Ideally, sqlc would either report an error with the statement in question to make this much easier to debug, or just ignore statements that are irrelevant to sqlc, like UPDATE. My current workaround is to create a small tool to remove these ETL steps before running sqlc generate.
Here's the full text of the panic (the line numbers are slightly off in parse.go, since I added logs, line 66 in the panic below is line 64 in the current master).
Using MySQL, I get a panic on
sqlc generate
. I've added some debug logs to narrow down the migration/statement causing the issue, and it's from an ETL step, which is in our migrations but doesn't need to be considered by sqlc:Ideally,
sqlc
would either report an error with the statement in question to make this much easier to debug, or just ignore statements that are irrelevant to sqlc, likeUPDATE
. My current workaround is to create a small tool to remove these ETL steps before runningsqlc generate
.Here's the full text of the panic (the line numbers are slightly off in parse.go, since I added logs, line 66 in the panic below is line 64 in the current master).
The text was updated successfully, but these errors were encountered: