MariaDB support: GENERATION_EXPRESSION is nullable #126
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
Member
|
Interesting... thanks for the PR. I'll poke at it some to make sure it won't break mysql. |
|
Any update on this one? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
MariaDB was designed to be a drop-in replacement for MySQL, so the codebase should be able to support it.
The only discrepancy I've encountered is that
INFORMATION_SCHEMA.COLUMNS.GENERATION_EXPRESSIONisNULLby default in MariaDB.This PR fixes #114, but haven't checked properly if it breaks anything elsewhere.