MySQL Reference Manual for version 4.0.18.
15.4 Feature Differences between MaxDB and MySQL
The following list provides a short summary of the main differences
between MaxDB and MySQL; it is not complete.
-
MaxDB runs as a client/server system. MySQL can run as a client/server system
or as an embedded system.
-
MaxDB might not run on all platforms supported by MySQL. For example,
MaxDB does not run on IBM's OS/2.
-
MaxDB uses a proprietary network protocol for client/server
communication, while MySQL uses either TCP/IP (with or without SSL
encryption), sockets (under Unix-like systems), or named pipes
(under Windows NT-family systems).
-
MaxDB supports stored procedures. For MySQL, stored procedures are
implemented in version 5.0. MaxDB also supports programming of
triggers through an SQL extension, which is scheduled for MySQL
5.1. MaxDB contains a debugger for stored procedure languages,
can cascade nested triggers, and supports multiple triggers per
action and row.
-
MaxDB is distributed containing user interfaces that are text-based,
graphical, or web-based. MySQL is distributed with text-based user
interfaces only; a graphical user interface (MySQL Control Center)
is shipped separately from the main distributions. Web-based user
interfaces for MySQL are offered by third parties.
-
MaxDB supports a number of programming interfaces also supported
by MySQL. However, MaxDB does not support RDO, ADO, or .NET, all of which are
supported by MySQL. MaxDB
supports embedded SQL only with C/C++.
-
MaxDB contains administrative features that MySQL does not have:
Job scheduling by time, event, and alert, and sending
messages to a database administrator on alert thresholds.
This document was generated
by rdg (Feb 25 2004)
using texi2html