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

Check for existing VS when creating a new one #54

Closed
kaklakariada opened this issue May 6, 2024 · 0 comments · Fixed by #55
Closed

Check for existing VS when creating a new one #54

kaklakariada opened this issue May 6, 2024 · 0 comments · Fixed by #55
Assignees
@kaklakariada
Labels
bug Unwanted / harmful behavior

Comments

@kaklakariada
Copy link
Collaborator

See exasol/extension-manager#177
To improve error messages for the user we need to check, if a virtual schema already exists with the same name before creating a new one.
@kaklakariada kaklakariada added the bug Unwanted / harmful behavior label May 6, 2024
@kaklakariada kaklakariada self-assigned this May 6, 2024
kaklakariada added a commit that referenced this issue May 6, 2024
@kaklakariada
#54 Increment version
ff8fd43
kaklakariada added a commit that referenced this issue May 6, 2024
@kaklakariada
#54: Check for existing VS
55ed250
@kaklakariada kaklakariada mentioned this issue May 6, 2024
Merged
kaklakariada added a commit that referenced this issue May 7, 2024
@kaklakariada @ckunki
#54: Check for existing instance before creating a new one (#55)
30134e6 
Co-authored-by: Christoph Kuhnke <github@kuhnke.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kaklakariada kaklakariada

Labels
bug Unwanted / harmful behavior
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#54: Check for existing instance before creating a new one exasol/extension-manager-interface
1 participant
@kaklakariada