-
Notifications
You must be signed in to change notification settings - Fork 546
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
down
and related commands fail [redshift]
#146
Comments
Hi, thanks for raising this issue. Postgres works like a charm! Anyone able to debug this further? I have no idea why Redshift would fail on a syntax that's part of this codebase since the beginning: Lines 61 to 76 in 7a98874
^ the |
I've added a ticket for my team to look into this, hopefully we can get to the bottom of it. It was member of our team (who has since left) that added Redshift support originally, so it might be up to us to keep it alive! |
It's Also I should mention that this bug is not brand new. We've had this issue for a little while now, I'd estimate a month or two. |
Sounds good. Thanks @eeshugerman! |
@eeshugerman hey, FYI, I accidentally figured out the bug when working on unrelated branch. Fixed in #156. |
@eeshugerman Please, report back if the fix is OK. Going to release v2.7.0-rc2. |
@VojtechVitek Sweet! Unfortunately I'm a golang noob. How do I build the new version? I did
|
@VojtechVitek I pulled the new changes today and the build worked, and yep the bug is fixed. Thanks for taking care of this so quickly! edit: hmm looks like there are no new commits to master since Tuesday, so not sure what went wrong with my |
Copy fix from pressly#146. At some point (probably after we upgrade our go version) we should update our goose fork from upstream.
down
,down-to
, andredo
fail like so:FAIL pq: operator does not exist: bigint =?, quitting migration
The source of this error is line
175194 ofmigration_sql.go
:tx.Exec(GetDialect().deleteVersionSQL(), v)
Apparently the
?
isn't getting replaced by the version number.Perhaps this has something to do with it?
I'm curious if Postgres users are running into this too.
The text was updated successfully, but these errors were encountered: