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

Subscribe to our news:
Partners
Testimonials
Michael Pavitsky: "SQL Maestro Group provided the kind of services and support for managing PostgreSQL data expected in a true business partnership. Their devotion to customer satisfaction and cost curtailment is a pleasure for PostgreSQL users. I wouldn?t hesitate to recommend PostgreSQL Data Wizard to any of my peers and I know and trust they will surpass all expectations".
Dave Lantz: "I have to say that I simple love this product and its ease of use. I know that I have only tapped into about 20% of what it can do. In my business I come into a lot of contact with developers and I tell them all, that if they need an easy way to connect, report or work their databases they MUST check out your products".

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