Choose your database:
AnySQL
MySQL
MS SQL Server
PostgreSQL
SQLite
Firebird
Oracle
SQL Anywhere
DB2
MaxDB

Subscribe to our news:
Partners
Testimonials
Charles Phillips: "I very much like the program and all of its functionality! Would be happy to give you an endorsement or recommend it to others - saves me a ton of time".
David Lantz: "Thank you, this is by far the simplest, and most friendly utility for building db record system I have ever used. I wish I could get my systems guys at the office to purchase this for our company would be so very helpful and speed up a lot of work. I for one have used it for everything from a simple inventory record of my house, to a members record for my church just little pet projects and a test bed to test my own db builds and theories before having to hand code at the office..... it is a lot of fun to work with".

More

Add your opinion

SQL Maestro Group / News / All company news / MySQL Maestro 1.4 released

MySQL Maestro 4.5 (former version 1.4) released

May 28, 2004

Prev Next

MySQL Maestro 4.5 released. Now it is possible to manage several table subobjects at once, e.g.

  • create/edit/drop all the indexes and foreign keys for a whole database. This feature is available in the Create Database Object dialog, which can be invoked from the Object menu;
  • drop several fields, indexes or foreign keys at a time for a table: just select required objects at the proper page of the Table Editor and simply press the Delete key;
  • copy several fields, indexes, or foreign keys from one table to another: you can do  it using standard Copy/Paste functions or by drag-n-drop between two instances of the Table Editor.

Several minor bugs were fixed:

  • there were some troubles with copying tables containing foreign keys from one database to another;
  • the Copy Database wizard did not copy tables with foreign keys properly in some cases. The "Disable foreign key checks" option was added to the final step of the wizard to avoid this problem;
  • the Windows -> Close All menu item did not closed all child windows in some cases;
  • the database explorer did not restore its width after sequential hiding and showing by its splitter.

Related links:

Prev Next