Bug #61006 Fixed generated database prefix and connection string in typed dataset - again

• Submitted: 29 Apr 2011 11:14
• Modified: 30 Jun 2011 20:13
• Reporter: Middle King
• Status: No Feedback
• Category: Connector / NET
• Severity: S1 (Critical)
• Version: 6.3.6
• OS: Windows (Windows 7)
• Assigned to: Assigned Account
• CPU Architecture: Any
• Tags: connection string in typed dataset, database prefix

[29 Apr 2011 11:14] Middle King

Description:
Hi there!

I am using the Connector version 6.3.6 have the same problem raised in the Bug #33870, #33870, and considered as duplicated one.

If I use stored procedure with params and specify their names without the databasename or schema prefix => the generated codes won't generate code for corresponding parameters.
 

How to repeat:
Just repeat as described in the two bugs: #33870, #33870 and the problem will be spotted right away.

Suggested fix:
When generate the code for the typed dataset, do get the database name/schema from the application connection string as in recommended in #33870, #33870.

[31 May 2011 20:13] Julio Casal

If reproduction steps for this issue are the same as for bug 33870, then I cannot reproduce the issue, as it is solved in 6.3.6.

Please provide specific reproduction steps for this scenario and, if possible, a sample database script and Visual Studio project to quickly reproduce the issue.

[1 Jul 2011 23:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".