Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix: postgres migration missing schema name #4164

Merged
merged 1 commit into from
Sep 21, 2022
Merged

fix: postgres migration missing schema name #4164

merged 1 commit into from
Sep 21, 2022
+10 −2

Conversation

krynble
Copy link
Contributor

@krynble krynble commented Sep 21, 2022 •
edited by netroy
Loading

Fixes #4163

netroy
netroy approved these changes Sep 21, 2022
View reviewed changes
Copy link
Member

@netroy netroy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@n8n-assistant n8n-assistant bot added core Enhancement outside /nodes-base and /editor-ui n8n team Authored by the n8n team labels Sep 21, 2022
@netroy netroy merged commit 2598ec8 into master Sep 21, 2022
@netroy netroy deleted the fix-migration-issue branch September 21, 2022 17:06
@n8n-assistant n8n-assistant bot added the Upcoming Release Will be part of the upcoming release label Sep 21, 2022
@janober
Copy link
Member

janober commented Sep 21, 2022

Got released with n8n@0.195.1

@janober janober removed the Upcoming Release Will be part of the upcoming release label Sep 21, 2022
valya pushed a commit to valya/n8n that referenced this pull request Nov 8, 2022
@krynble
fix: postgres migration missing schema name (n8n-io#4164)
d263a87
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@netroy netroy netroy approved these changes

Assignees
No one assigned
Labels
core Enhancement outside /nodes-base and /editor-ui n8n team Authored by the n8n team
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Latest version error on migration with postgres
3 participants
@krynble @janober @netroy