MySQL Bugs: #63480: Typed Dataset Designer gets into long slow loop on query configure

Bug #63480	Typed Dataset Designer gets into long slow loop on query configure
Submitted:	29 Nov 2011 20:26	Modified:	7 Sep 2012 22:28
Reporter:	Aron Miller	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S5 (Performance)
Version:	6.4.4	OS:	Windows (XP SP3)
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	TypedDataset, VisualStudioDesigner

Description:
When using the XSD typed data set designer and adding queries to tables, it is consistently the case that after a few queries are added the system grinds to a crawl taking 5+ minutes to complete each step in the process. 

The query log provides some insight. The system appears to get into a very long loop of a handful of information_schema queries. When things are going well these queries are made, but not in such vast numbers.

e.g. Query log (this repeats 100s of times -- I've obscured the table names)
103 Query	SHOW INDEX FROM `xxx`.`yyy`
103 Query	SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE != 'VIEW' AND TABLE_SCHEMA LIKE 'xxx' AND TABLE_NAME LIKE 'yyy' AND TABLE_TYPE LIKE 'BASE TABLE'
103 Query	SHOW INDEX FROM `xxx`.`yyy`
103 Query	SELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA LIKE 'xxx' AND TABLE_NAME LIKE 'yyy'
103 Query	SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE != 'VIEW' AND TABLE_SCHEMA LIKE 'xxx' AND TABLE_NAME LIKE 'yyy'
103 Query	SELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA LIKE 'xxx' AND TABLE_NAME LIKE 'yyy'
103 Query	SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE != 'VIEW' AND TABLE_SCHEMA LIKE 'xxx' AND TABLE_NAME LIKE 'yyy'
103 Query	SELECT * FROM INFORMATION_SCHEMA.VIEWS WHERE TABLE_SCHEMA LIKE 'xxx' AND TABLE_NAME LIKE 'yyy'
103 Query	SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE != 'VIEW' AND TABLE_SCHEMA LIKE 'xxx' AND TABLE_NAME LIKE 'yyy' AND TABLE_TYPE LIKE 'BASE TABLE'
103 Query	SHOW INDEX FROM `xxx`.`yyy`

How to repeat:
Database is approximately 60 tables with minimal amount of data. Working from a database of this profile on XP3, connector/net 6.4.

It's plausible that this is more likely of an issue on tables with more foreign keys, but it seems rather nondeterministic and I'm not certain of that.

Suggested fix:
I don't have enough insight into what is driving the problem to suggest a fix. Perhaps I need to debug the source myself?

What exact version of Connector/Net, 6.4.x, do you use?

(adjusting version to specify more precise version 6.4 -> 6.4.4)

Same behavior for versions 6.2.5 and 6.3.7.

Hi Aron,

Thanks for your bug report.

Can you provide more information on how to repro? specifically
a) A sample of the kind of queries you are adding to the typed data sets.
b) A sample data model.

Note. I have tried to repro this using adding 60 tables to a typed data set (each table with a foreign key) and some queries, yet have not being able to see the slow down behavior.

We've moved on to another provider, and I regret I won't have time to followup on this. Perhaps if someone else has this bug then they will discover this entry.

Also, this was on VS2008. Thanks.

Not enough info has been provided to reproduce this issue, please check the page http://bugs.mysql.com/how-to-report.php.