Kieran, thanks for this idea. I think the GUI part would be less important for Drupalers than other aspects of MySQL since we mainly use it from PHP. Performance would be something to look forward to. Other points: - How much performance degradation does InnoDB introduce? We all know InnoDB is good for referential integrity, transactions, ...etc. but it does increase overhead. How much of that is expected for a CMS type application. - Is MySQL planning to do away with the serious drawback of not complaining about syntax that is not supported by the current engine? For example, if you give an option that requires InnoDB to work, but you are using MyISAM, it will silently accept it, without complaining, giving the user a false sense that the operation was successful. On 8/23/05, Kieran Lal <kieran@civicspacelabs.org> wrote:
Hello, as a follow up to OSCON I have arranged a chat with the MySQL development team. I met and talked with one of the founders of MySQL, David Axmark. I suggested that the Drupal community would like to learn how to better use MySQL as well as provide feedback to the developers so that they understand our requirements in the design of Drupal.
I would like to put performance as one of the top points of discussion. David suggested a few topics as well: the optimizer, gui tools, PHP driver or the prepared statment support. Depending on what we want to talk about he will have the right team members attend the chat.
Let's get a list of prioritized topics to discuss and then work on a mutual meeting time.