MySQL Bugs: #33870: Generated database prefix and connection string

Bug #33870	Generated database prefix and connection string
Submitted:	14 Jan 2008 17:36	Modified:	13 Jul 2010 13:51
Reporter:	Renaud Paquay	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	5.1.4, 5.2.4	OS:	Windows (Vista)
Assigned to:	Reggie Burnett	CPU Architecture:	Any
Tags:	table prefix connection string

Description:
The problem appears when using Data Provider for MySql and strong typed DataSet.

I develop my application using strong typed datasets.

When I drag and drop a table into the xsd, a code is auto generated which contains the connection, the select statement, and so on.

The problem is that the generated code contains the dabase prefix like :
SELECT `ID`,`Name` from `databaseName`.`Customers`;

When using strong typed dataset, the connection is normally created with :
global::<myNameSpace>.Properties.Settings.Default.<myConnectionStringName>

When I change the Application setting in my app.exe.config, due to the database prefix, nothing changes.

How to repeat:
Create a new application with a MySqlData Provider for mysql.

Drop a table into a new xsd.

Go to the <MyDataSetName>.Designer.cs

Observe the generated update or select commands.

Suggested fix:
Do not generate the database prefix as it should be defined at Application Setting level.

Hello,
I completly agree with Renaud, the database prefix is a real problem.

1. When changing from development database to test database then production database, names are not same.
2. When hosting several times the same application that need distinct database for each instance.

Regards,
Cyrille

problem persists with version 5.2.2

Hi Renaud and thanks for your report.

I can't make up my mind on how to treat this problem as both approaches have their good and bad side. But I am setting report to verified on the bases of inconsistency:
  Looking into autogenerated, for example, UPDATE command one sees "database." prefix but if you open same command in query builder the prefix is gone. This should at least look/behave in uniform fashion.

Verified as described.

DB prefix present in object explorer

Attachment: BUG33870-1.JPG (image/jpeg, text), 47.44 KiB.

DB prefix *not* present in QB (same command)

Attachment: BUG33870-2.JPG (image/jpeg, text), 33.13 KiB.

To be checked together with Bug#38922.

Bug#38922 was marked as duplicate of this report.

Bug#46930 was marked as duplicate of this report.

Error generated when removing database name from CommandText

Attachment: sproc-param-error.PNG (image/png, text), 13.25 KiB.

Downgrading this to medium since there is a valid workaround.

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/112800

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/112801

fixed in 6.0.7, 6.1.5, 6.2.4, and 6.3.3+

An entry has been added to the 6.0.7, 6.1.5, 6.2.4, and 6.3.3 changelogs:

Database name was emitted into typed datasets. This prevented users using the configured default database.