phpMyAdmin 2.5.1 Released

By Deane Barker on June 2, 2003

Everyone’s favorite Web-based database management interface has released a new version with some snazzy improvements. Some highlights:

* Displays results for multi-statement SQL requests
* Saves export files to the server on which it’s running (previously, you had to save them locally)
* Displays the last-inserted auto-increment field (handy for getting keys back if you’re manually inserting foreign keys in another table)

phpMyAdmin is an un-abashed success story. I wish they had ODBC support so I could manage non-MySQL databases from it. From the beginning, it’s been designed with the user in mind and its wild popularity is a testament to that strategy.



  1. I agree about phpMyAdmin and have also recently upgraded. I’ve been meaning to try Control Center by the makers of MySQL – I’ve got to think it’s pretty good too, have you tried it?

  2. I didn’t even know about it until you mentioned it, but I downloaded it tonight. Very, very slick. This is the UI that MySQL has always been missing.

    For people from the Windows world, this is essentially Enterprise Manager for MySQL. I’ve only spent 10 minutes with it, but I can’t see how you’d need anything else to manage the server. You can create and modify tables, add and delete records, check server statistics, manage multiple servers, etc.

    This should speed MySQL adoption quite a bit. A lot of people have always been spooked by the command line (I’ve grown to like it, actually).

  3. They can have (some) ODBC support for the cost of a relink…

    OpenLink Software, , the folks who maintain and support the cross-platform open-source iODBC (Independent ODBC) Driver Manager project (and who employ me, mostly in a Support role), recently made a new project available through the website — .

    The MySQL -> ODBC Gateway, , is an open-source bridging library to which MySQL-bound applications may be relinked, instantly making any application which has been written to standards, database agnostic. There are some MySQL API calls which haven’t been mapped to ODBC yet — but the bulk of the work is done.

    Lots of application designers have worked with MySQL, because it was free, and then found that enterprises didn’t want their application, because it was tightly bound to MySQL, which wasn’t certified for their enterprise, or which would have required lots of learning to integrate.

    We decided to produce the MySQL -> ODBC Gateway to enable these designers to bring their applications to the enterprise — on whatever ODBC compliant back-end that enterprise wished. Oracle, MS SQL Server, Virtuoso, Informix, Progress, Ingres — all of these, and many more, are now within reach, with a far smaller learning curve. The application designer also has far less work to do to make their application work with other implementations of SQL than has been the case to date.

    I’d love to see phpMyAdmin relinked, and hear how it works with other ODBC-compliant DBMS… It’s on my own project list, but as that continues to expand without limit, it may be a while before I get to it…

Comments are closed. If you have something you really want to say, tweet @gadgetopia.