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.

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

Hotfix for postgres db backend #145

Merged
merged 3 commits into from
Oct 4, 2024
Merged

Hotfix for postgres db backend #145

merged 3 commits into from
Oct 4, 2024

Conversation

lennartdohmann
Copy link
Contributor

No description provided.

lennartdohmann and others added 3 commits October 2, 2024 09:36
@unglaublicherdude
Copy link
Member

dunno. most of these changes are the scoping. Wasn't that stuff already backported?

@lennartdohmann
Copy link
Contributor Author

lennartdohmann commented Oct 4, 2024

dunno. most of these changes are the scoping. Wasn't that stuff already backported?

Yes, this is already in there, it is only displayed because we have backported but we should always merge main to v30 for the sake of simplicity. The relevant change here is only in the DBMapper of the Postgres string. But this small change just blocks the complete functionality of the app when using Postgres.
Also it effects only version 30.

@lennartdohmann lennartdohmann merged commit 9a989b5 into v30 Oct 4, 2024
6 checks passed
lennartdohmann added a commit that referenced this pull request Oct 22, 2024
Hotfix for Postgres user

(cherry picked from commit 9a989b5)
lennartdohmann added a commit that referenced this pull request Oct 23, 2024
Hotfix for Postgres user

(cherry picked from commit 9a989b5)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants