fix: exception when calling database #63
Merged
Conversation
This file contains hidden or 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
There appears to be a bug in the current version of the MySQL entity framework implementation where using the string's ".Equals" results in a "LCASE" command that throws a null reference exception. Since MySQL is not case sensitive we can simple remove this part of the database calls for now...
ProgrammingByPermutation
force-pushed
the
bug/DbCrash
branch
from
ffc0828 to
0003a66
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There appears to be a bug in the current version of the MySQL entity framework implementation where using the string's ".Equals" results in a "LCASE" command that throws a null reference exception. Since MySQL is not case sensitive we can simple remove this part of the database calls for now...