We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Submitted by: Toni Martir (toni_martir)
Votes: 1
When fetching rows, reading string column values calls public static Charset GetCharset(string charsetName)
Replacing the sequential search with a dictionary there is a 80% performance gain when reading strings:
private static Dictionary<string, Charset\> supportedCharsetsNames; public static Charset GetCharset\(string charsetName\) \{ return supportedCharsetsNames\[charsetName\]; \}
And inside InitializeSupportedCharsets:
supportedCharsetsNames = new Dictionary<string, Charset\>\(\); foreach \(Charset ncharset in charsets\) \{ supportedCharsetsNames\.Add\(<http://ncharset.name>, ncharset\); \}
Commits: b750ac8
The text was updated successfully, but these errors were encountered:
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
Fix Version: vNext [ 10640 ]
Sorry, something went wrong.
cincuranet
No branches or pull requests
Submitted by: Toni Martir (toni_martir)
Votes: 1
When fetching rows, reading string column values calls public static Charset GetCharset(string charsetName)
Replacing the sequential search with a dictionary there is a 80% performance gain when reading strings:
And inside InitializeSupportedCharsets:
Commits: b750ac8
The text was updated successfully, but these errors were encountered: