Re: Aderministrator + Query_browser = Great!!!
Posted by: Michael G. Zinner
Date: May 31, 2005 12:10PM


we decided to split the functionality into seperate tools, because a Database Administrator has a different need than a Developer.

The MySQL Administrator is used to configure the MySQL server. Once it is up and running, you just need it to do backups or create a user account from time to time.

On the other hand a developer who is developing a database application should not change any server configuration or create user accounts. He just needs to write SQL queries and scripts and work with resultsets. So the MySQL Query Browser is the tool to use for him.

Never the less MySQL Administrator and MySQL Query Browser can interact with each other and start each other if necessary.

If you want to get away from such tools like MS Access and move to a more professional client-server or application server environment, you will see that the way that we go makes sense.

About the Migration Toolkit. It is a native application that makes use of a Generic Runtime Environment that allows us to write modules in Java, PHP, C, Lua, ... For the Migration Toolkit we decided to use mostly Java modules because of the large number of JDBC drivers that are available.

I hope this gives you some insight.

Best regards,

Michael Zinner, Team Lead, Developer Tools

Are you MySQL certified?

Options: ReplyQuote

Written By
Re: Aderministrator + Query_browser = Great!!!
May 31, 2005 12:10PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.