Disable table metadata caching mechanism #201
Merged
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
This should prevents "unknown column" error after a column addition if the schema is needed or if data are to be inserted.
This was referenced Feb 29, 2016
HavokInspiration
added a commit
that referenced
this pull request
Mar 3, 2016
Disable table metadata caching mechanism
|
Thanks for this change :) |
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.
If the Schema metadata are generated and put in the cache and a column is added to a table, when doing a data insertion or update, it can results in error because the new column is not in the schema (because metadata are fetched from the cache).
This change completely disables the cache metadata feature.
Refs #199