Sun Tech Days St. Petersburg was on Wednesday-Thursday the last week and we’ve had a MySQL booth there. Unlike the last year, we’re full part of Sun now so managed to get a decent-sized booth, arrange for leaflets, and Kostja gave an overall MySQL talk.
Questions at the booth (in no particular order):
- When will Connector.NET support LINQ Entity framework? (According to Reggie Burnett: it is currently supported in Connector 6.0/Beta, which is expected to be GA soon)
- Can Connector.Net be used with Mono? (Yes)
- Is Workbench available for Linux (Yes)
- When will MySQL support stored procedures? This question seems to have replaced the infamous “When will MySQL support transactions” question.
- What is the impact of different transaction isolation levels on performance of InnoDB? (no idea. If you ran some experiments please drop a comment)
- When will MySQL support LIMIT clause inside subqueries, in particular the
... WHERE IN (SELECT ... ORDER BY LIMIT n)form? (we would like to add support for this, but no plans ATM. Request taken.)
- Does MySQL have any limitations on table/database size or number of records in the table? (I gather people are used to having limitations in free versions of SQL Server or Oracle and expect something like that in MySQL)
- When will fulltext search support searching for different wordforms (that’s a big deal for searching in Russian texts, as the words get different suffixes depending on which grammatic case they are in)? No plans ATM. Perhaps somebody has developed a fulltext parser plugin somewhere?
- When will InnoDB get efficient support for COUNT(*)?
- Are there any plans to make MySQL more efficient when handling big blob columns?
We’ve got several complaints that look like bugs:
- LEFT JOIN and multi-table DELETE fails to delete records when using foreign keys. We’ve got a test case so I’ve filed this as BUG#44207.
- There’s something wrong with Connector/Java and timezones. I’m not sure if we’ve managed to repeat the problem on our laptops, we were promised a bug report.
- Another person complained about a sharp slowdown in join performance when table size(s) exceed 1M rows. According to the reporter, all buffers are adequately-sized, EXPLAIN shows that the query plan is the same. No idea what this could be then, as the SQL layer doesn’t have any hard-coded buffer sizes.