-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Vendor complete set of migrate drivers #16420
Comments
@wy65701436 @stonezdj I'm not sure I understand "help wanted" on this issue. Per Even so, I was experimenting with changing the module vendoring just to see if I could close the issue, and found that:
In short, what help can the community provide on this issue? |
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue. |
Is there a chance this could be re-opened and addressed? It would be great if:
While the second point might be less straightforward to implement, the first one should be trivial. What would be the best way to move this forward, @wy65701436 @stonezdj ? |
I'm trying to address #8649 and finding that, while I can reproduce the
pg_advisory_lock
issue in tests, when I try to switch the migrator to usecockroachdb
I run into trouble. It seem that thedatabase
directory ingolang-migrate/migrate
has been stripped back to justpostgresql
.Would you please restore the
database
directory of that package? Or at leastdatabase/cockroachdb
?Thanks very much.
The text was updated successfully, but these errors were encountered: