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

Foreign key definitions should not set explicit schema names #1198

Closed
stefanomorson opened this issue Dec 14, 2017 · 0 comments · Fixed by #1213
Closed

Foreign key definitions should not set explicit schema names #1198

stefanomorson opened this issue Dec 14, 2017 · 0 comments · Fixed by #1213
Assignees
@Coduz
Labels
Bug This is a bug or an unexpected behaviour. Fix it!

Comments

@stefanomorson
Copy link
Contributor

Description:
Scripts in kapua-foreignkeys do set a explicit schema name. This approach limits the portability of the function. Tests for example, use a different schema name (PUBLIC) so deletes does not work properly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Coduz Coduz

Labels
Bug This is a bug or an unexpected behaviour. Fix it!
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Removed schemaName property from Liquibase XMLs eclipse-kapua/kapua
2 participants
@Coduz @stefanomorson