MySQL Bugs: #44715: Double authorization when altering SP in server explorer

Bug #44715	Double authorization when altering SP in server explorer
Submitted:	7 May 2009 11:32	Modified:	13 Aug 2010 14:29
Reporter:	Tonci Grgin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / NET	Severity:	S3 (Non-critical)
Version:	6.0.3	OS:	Windows (2K8 x64)
Assigned to:	Vladislav Vaintroub	CPU Architecture:	Any
Tags:	VS plug-in

Description:
Opening connection in server explorer and choosing to alter existing routine requires another authentication at server.

How to repeat:
VS2008Pro, c/NET 6.0.3GA, Win2K8x64.

 - Created DataConnection to remote box, database test, via it's IP (then 192.168.1.2). 192.168.1.2(test)
 - Created new DataConnection to remote box by it's name (OpenSol), database test, while it's IP was still 192.168.1.2. opensol(test).
 - Changed OpenSol IP to 192.168.1.12
 - Open VS2008, dbl-click on opensol(test) connection, show SP's, all is fine
 - Right-click any SP, choose "Alter Routine"
 - Change stuff
 - When trying to apply the changes, VS2008 pops-up MySQL server login where server is represented by old IP, 192.168.1.2 and fails as there is no such box any more.

Question is, if this is a bug in c/NET and not VS, why am I asked for credentials (and wrong ones) while still connected to remote MySQL server in server explorer.

Suggested fix:
-

Clicking "Cancel" solves the problem of altering SP.

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

833 Vladislav Vaintroub	2010-08-12
      Bug#44715 :  Double authorization when altering SP in server explorer .
      
      The problem was that editing stored procedure (or trigger) caused the whole Date Explorer
      to be refreshed, including  database nodes different from active one.
      
      Refresh on DataExplorer window would  attempt to reopen connections that were broken,
      hence triggering authorization dialogs.
      
      The fix is to refresh only the current database node.
      
      This patch also fixes broken editing triggers in VS2008. Trying to get parent node of trigger
      in the hierarchy fails with COM error.  The patch implements more robust way to get table 
      name of the trigger (extracts it from trigger text)

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

Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server.