Bug #14576 Contradiction in documentation of useUnicode connection property

• Submitted: 2 Nov 2005 15:27
• Modified: 30 Jul 2006 7:42
• Reporter: Yair dfwerfw
• Status: Closed
• Category: Connector / J Documentation
• Severity: S3 (Non-critical)
• Version: 3.1.11
• Assigned to: MC Brown
• CPU Architecture: Any

[2 Nov 2005 15:27] Yair dfwerfw

Description:
In the connection properties table, the Default Value column for property useUnicode is 'false', while the property's Definition claims it "defaults to 'true'"

How to repeat:
N/A

Suggested fix:
N/A

[6 Nov 2005 10:36] Vasily Kishkin

Sorry...What do you mean "property's Definition" ? Could you please create and attach simple test case ?

[7 Nov 2005 6:57] Yair dfwerfw

Vasily, sorry about the confusion.
This bug refers to the documentation of Connector/J 3.1.11

In "Table 1. Connection Properties" the property useUnicode is described as

"Should the driver use Unicode character encodings when handling strings? Should only be used when the driver can't determine the character set mapping, or you are trying to 'force' the driver to use a character set that MySQL either doesn't natively support (such as UTF-8), true/false, defaults to 'true'"

while next to this description in the column for "Default Value", it is listed as "false"

[7 Nov 2005 6:58] Yair dfwerfw

So it is not clear from the documentation whether the default value is true or false

[15 Nov 2005 21:31] Vasily Kishkin

Sorry....I was not able to find this URL. Can you advise me it ?

[17 Nov 2005 9:02] Yair dfwerfw

http://dev.mysql.com/doc/refman/5.0/en/cj-configuration-properties.html

search for "useUnicode" entry in the table

[23 Nov 2005 12:38] Vasily Kishkin

Thanks for URL. I found. I think it will be corrected as soon as possible.

[30 Jul 2006 7:42] MC Brown

Fixed in the latest properties table update.