Designing & Engineering MySQL
Databases
Introduction
MySQL
is the world’s most popular open source database. Visual case provides full
support for the most used
features.
Using
Visual Case to Design MySQL Databases
A MySQL database can be built in Visual Case
using the design tools or by reverse engineering an existing
database. If a design already exists for a database of a different
type it can be converted to MySQL.
For an
introduction to database design, visit our database design
tutorial.
Tables –
Tables can be defined with any of the standard storage types
(MyISAM, InnoDB etc.).
Columns –
These are built in the table property page.
Data-types –
Visual Case supports all of the standard data types.
Autonumber – Autonumber columns are supported.
Visual Case always creates a primary
index on autonumber columns.
Foreign
Keys – These are supported for
InnoDB table types with restrict, set null, default or cascade on
delete. On update can restrict or cascade. Setting the child
cardinality will synchronize the "allow null" option on the foreign
key columns and create a unique index if the cardinality is "one
only".
Engineering MySQL Databases
Visual Case's database engineering wizard will forward and
reverse engineers all database attributes that can be defined in your
Visual Case design of a MySQL database.
The
wizard allows you to compare the differences between your database
design and the physical database before completing either the
forward or the reverse engineer.
The
forward engineer builds a SQL script that can be saved and
manually run at a later time.
You
can quickly forward-engineer a single entity (table, stored
procedure, etc.) from its right-click menu or from its property
page.
For
more information about forward and reverse-engineering databases,
please visit our database engineering
tutorial.
Migrating to MySQL
Visual Case will convert any supported database
type to MySQL. Visual Case will also reverse engineer most ODBC or
JDBC data sources to MySQL, even if the physical database is not a
type directly supported by Visual Case.
Because of differences
between database data types conversion is usually a one-way process.
For example, converting a SQL Server varchar(300) column to Access
will produce a column of type memo as Access’s text data type is
limited to 255 characters. Converting back to SQL Server will
produce a column of type text as a memo column can be quite
long!
Free Trial Download
Finally, download the 30 day free trial of
Visual Case and get started.
Visual CaseTM is a trademark or
registered trademark of Artiso Corp. Canada.
Microsoft,
Windows, SQL Server, VB, Visual Basic and Access are registered
trademarks of Microsoft Corporation.
Oracle is a registered
trademark of Oracle Corporation.
Unified Modeling Language and
UML are trademarks of Object Management Group Inc. in the U.S. and
other countries.
Other brands and their products are trademarks
or registered trademarks of their respective holders and should be
noted as such.
This site is best viewed at a resolution of 800 by
600 using Internet Explorer 5.
|
