This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
BZ-1231014 Fixed case sensitive issue for mysql #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I agree that this should be merged. Unless there is some work around I am missing, this is a breaking issue for people using MySQL (or any other case sensitive database) |
|
Reviewed & merged on both master & 6.3.x |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This issue belong to Mysql case sensitive.
Because of, in jbpmKPI_v2.kpis, we use lowercase of tables name.
Like, we use processinstancelog instead of ProcessInstanceLog.
If i change it, it will be ok.
IMO, other database also have case sensitive issue.
Please review it