MySQL Bugs: #51209: error on parameter without value on connectionstring

Bug #51209	error on parameter without value on connectionstring
Submitted:	16 Feb 2010 15:11	Modified:	17 Feb 2010 15:07
Reporter:	Jorge Bastos	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	6.2.2	OS:	Any
Assigned to:	Reggie Burnett	CPU Architecture:	Any

Description:
Howdy,
A connection string like this:

"character set=utf8;pooling=false;compress=;Persist Security Info=False;Connect Timeout=30;Data Source=localhost;Database=mydb;User ID=myuser;Password=mypwd;Port=3306"

Will generate an error, cause of the missing value on "compress="

I didn't tried on other parameters, but they may raise an error aswell.
When the value is missing on the connection string, it should fallback to the default value of the parameter when it is not specified on the CS.

How to repeat:
Create a CS with a parameter without assigned value, like:
"compress="

Hi Jorge and thanks for your report. I fail, however, to see what's S2(serious) about this? You malformed the connection string and it errors out. Your report is looking more like feature request to me...

Verified as described using trunk. Some values are filled in automagically (like port or logging) while others are not (charset=; compress=;). This behavior is not uniform across the parameters and it should be imo.

Hi Tonci,
Sorry about the severity, my error!
Yap, this should be filled automatic, even that the values are wrong inserted in the CS like I provided.
pooling and compress have both this problem I believe.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/100557

830 Reggie Burnett	2010-02-16
      - fixed bug where giving a connection string option like (option=) and then trying to read
        the option back via the property would fail (bug #51209)

fixed in 6.2.3 and 6.3.1+

Thank you Reggie :-)

An entry has been added to the 6.2.3, 6.3.1 changelogs:

Specifying a connection string where an option had no value generated an error, rather than the value being set to the default. For example, a connection string such as the following would result in an error:

server=localhost;user=root;compress=;database=test;port=3306;password=123456;