Bug #8387 | Connecting with NAMES and character_set_results can be up to 18 times slower. | ||
---|---|---|---|
Submitted: | 9 Feb 2005 6:36 | Modified: | 22 Jun 2005 21:13 |
Reporter: | Lynn Eriksen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / NET | Severity: | S1 (Critical) |
Version: | 1.0.4 | OS: | Windows (WinXP/Win2003) |
Assigned to: | Reggie Burnett | CPU Architecture: | Any |
[9 Feb 2005 6:36]
Lynn Eriksen
[27 Feb 2005 2:10]
Lynn Eriksen
This does not happen with 4.1.10.
[22 Jun 2005 21:13]
Reggie Burnett
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html Additional info: I changed the code to only do the set names if the connection or client charset is different than what we already have. However, I am still setting the results charset to NULL to prevent the server from converting all results to a single charset. I could add some type of connection string option that would a user would set if they are sure they are always going to be using the charset on the server. However, with connection pooling I am not sure how much this will help. If you are seeing perf problems, perhaps you need to better tune your connectoin pools?