Bug #25318 Query Builder does not show Tables
Submitted: 28 Dec 2006 20:34 Modified: 2 Sep 2009 9:06
Reporter: Mike Gerschefske Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Visual Studio Plugin Severity:S4 (Feature request)
Version:1.0.2/5.0.2 OS:Windows (WinXP)
Assigned to: CPU Architecture:Any

[28 Dec 2006 20:34] Mike Gerschefske
Description:
When building queries with the query builder no tables show up in the Add Table option.

How to repeat:
This is probably a round about way of doing this...

Create a data access layer by "Add New Item" and select the dataset icon.  In there a wizard pops up then select connection string (or make one).  Select use sql statements then hit next.  Press teh Query Builder button and the Add Table dialog pop's up with no tables in it.

Suggested fix:
Maybe do a "SHOW TABLES" query and somehow populate this box?  Not sure how the API works.
[28 Jan 2007 13:48] djam djam
I have the same problem, any idea??
[24 Apr 2009 14:22] Christian H. Pedersen
I had this problem as well. I sweated over it for a while, struggling with the MySQL Administrator in search of a way to set permissions because I thought the missing tables were due to the user being unable to view the tables in question.

It turns out it isn't a permissions problem. It's a bug in the integration with Visual Studio 2008 that causes the list of available tables to fail to populate. If you know the name of the table you need to add to your table adapter, you can construct the adapter's query manually - Just write the SQL yourself rather than relying on selecting it from the list:

SELECT *
FROM [name of table]

Try to hit Execute Query here. For me, this caused the entire query builder window to update itself with all the necessary information. On "Finish", the adapter got added to the dataset correctly.
[9 May 2009 5:46] A de koning
isn't this fixed yet???
[2 Sep 2009 9:06] Tonci Grgin
Sorry i missed this guys, this was no feature request but a valid bug report...

c/NET 5.0 is no longer supported and I verified 5.2 and 6.x work flawlessly with my VS2008Pro.

Closing the report now.