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

Concern superuser login on receiving schema #969

Merged
merged 2 commits into from
Oct 15, 2024
Merged

Conversation

signedav
Copy link
Member

No description provided.

@signedav
Copy link
Member Author

signedav commented Oct 10, 2024

  • Database or schema does not exist <-- can b e optimized

Copy link
Collaborator

@gacarrillor gacarrillor left a comment

Choose a reason for hiding this comment

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

Good! I stumbled upon this issue recently.

@gacarrillor
Copy link
Collaborator

gacarrillor commented Oct 10, 2024

  • Database or schema does not exist <-- can b e optimized

Is it related to this issue?
#967

@signedav
Copy link
Member Author

Is it related to this issue?
#967

Stumbled over this when I tried to fix 967 - there I cannot reproduce it, but maybe they are connected. Asked the user to test it..

@gacarrillor
Copy link
Collaborator

Is it related to this issue?
#967

Stumbled over this when I tried to fix 967 - there I cannot reproduce it, but maybe they are connected. Asked the user to test it..

I remember I saw that message (Database or schema does not exist) once, and had no clue about what happened. Don't remember anymore the situation or how to reproduce, though.

@signedav signedav merged commit 48ceb0a into master Oct 15, 2024
7 checks passed
@signedav signedav deleted the fixmodelreload branch October 15, 2024 10:36
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.

2 participants