| List: | Internals | « Previous MessageNext Message » | |
| From: | stefan | Date: | September 6 2005 5:11pm |
| Subject: | bk commit - mysqldoc@docsrva tree (stefan:1.3484) | ||
| View as plain text | |||
Below is the list of changes that have just been committed into a local mysqldoc repository of stefan. When stefan does a push these changes will be propagated to the main repository and, within 24 hours after the push, to the public repository. For information on how to access the public repository see http://www.mysql.com/doc/I/n/Installing_source_tree.html ChangeSet 1.3484 05/09/06 17:11:55 stefan@stripped +2 -0 maxdb.en.xml: Overwrite existing MaxDB section contents with what Ulf sent in (reworked by Ulf, and SAP Berlin) titles.ent: Add titles for MaxDB sections refman-common/maxdb.en.xml 1.3 05/09/06 17:11:12 stefan@stripped +409 -712 Overwrite existing MaxDB section contents with what Ulf sent in (reworked by Ulf, and SAP Berlin) refman-common/titles.ent 1.27 05/09/06 17:10:53 stefan@stripped +2 -0 Add titles for MaxDB sections # This is a BitKeeper patch. What follows are the unified diffs for the # set of deltas contained in the patch. The rest of the patch, the part # that BitKeeper cares about, is below these diffs. # User: stefan # Host: apollon.site # Root: /home/stefan/bk/mysqldoc --- 1.2/refman-common/maxdb.en.xml 2005-09-06 16:05:37 +02:00 +++ 1.3/refman-common/maxdb.en.xml 2005-09-06 17:11:12 +02:00 @@ -7,726 +7,423 @@ <!ENTITY % title.entities SYSTEM "titles.ent"> %title.entities; ]> -<section id='maxdb'> + <section id='maxdb'> <title id='title-maxdb'>&title-maxdb;</title> <para> - MaxDB is an enterprise-level database. MaxDB is the new name of a - database management system formerly called SAP DB. + MaxDB is an heavy-duty enterprise database. The database management + system is SAP-certified. </para> - <section id="maxdb-history"> - - <title id='title-maxdb-history'>&title-maxdb-history;</title> - - <para> - The history of MaxDB goes back to SAP DB, SAP AG's DBMS, i.e. - MaxDB is a re-branded and enhanced version of SAP DB. For many - years, MaxDB has been used for small, medium, and large - installations of the mySAP Business Suite and other demanding SQL - applications requiring an enterprise-class DBMS with regard to the - number of users, the transactional workload, and the size of the - database. - </para> - - <para> - SAP DB was meant to provide an alternative to third-party database - systems such as Oracle, Microsoft SQL Server, and DB2 by IBM. In - October 2000, SAP AG released SAP DB under the GNU GPL license - (see <xref linkend="gpl-license"/>), thus making it open source - software. - </para> - - <para> - Today, MaxDB is used in about 3,500 SAP customer installations - worldwide. Moreover, the majority of all DBMS installations on - Unix and Linux within SAP’s IT department rely on MaxDB. MaxDB - is tuned towards heavy-duty online transaction processing (OLTP) - with several thousand users and database sizes ranging from - several hundred GB to multiple TB. - </para> - - <para> - In 2003 SAP and MySQL concluded a partnership and development - cooperation agreement. As a result, SAP's database system SAP DB - has been delivered under the name of MaxDB by MySQL since the - release of version 7.5 (November 2003). - </para> - - <para> - Version 7.5 of MaxDB is a direct advancement of the SAP DB 7.4 - code base. Therefore, the MaxDB software version 7.5 can be used - as a direct upgrade of previous SAP DB versions starting 7.2.04 - and higher. - </para> - - <para> - Now, as before, the former SAP DB development team at SAP AG is - responsible for developing and supporting MaxDB. Both SAP AG and - MySQL AB handle the sale and distribution of MaxDB. The - advancement of MaxDB and the MySQL Server leverages synergies that - benefit both product lines. - </para> - - <para> - MaxDB is subjected to SAP AG's complete quality assurance process - before it is shipped with SAP solutions or provided as a download - from the MySQL site. - </para> - - </section> - - <section id="maxdb-licensing"> - - <title id='title-maxdb-licensing'>&title-maxdb-licensing;</title> - - <para> - MaxDB can be used under the same licenses available for the other - products distributed by MySQL AB. Thus, MaxDB is available under - the GNU General Public License, and a commercial license. For more - information on licensing, see - <ulink url="http://www.mysql.com/company/legal/licensing/"/>. - </para> - - <para> - MySQL offers MaxDB support to non-SAP customers. - </para> - - </section> - - <section id="maxdb-links"> - - <title id='title-maxdb-links'>&title-maxdb-links;</title> - - <para> - The main page for information about MaxDB is - <ulink url="http://www.mysql.com/products/maxdb"/>. Information - formerly available at <ulink url="http://www.sapdb.org"/> is only - related to releases 7.3 and 7.4 and is no longer maintained. - </para> - - </section> - - <section id="maxdb-basics"> - - <title id='title-maxdb-basics'>&title-maxdb-basics;</title> - - <para> - MaxDB operates as a client/server product. It was developed to - meet the needs of installations in OLTP and Data - Warehouse/OLAP/Decision Support scenarios. - <emphasis role="bold">Benefits:</emphasis> - - <itemizedlist> - - <listitem> - <para> - <emphasis role="bold">Easy configuration and - administration:</emphasis> GUI-based Installation Manager - and Database Manager as single admin tools for DBMS - operations - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Around-the-clock operation, no planned - downtimes, no permanent attendance required:</emphasis> - Automatic space management, no need for reorganizations - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Elaborate backup and restore - capabilities:</emphasis> Online and incremental backups, - recovery wizard to guide you through the recovery scenario - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Supports large number of users, - database sizes in the terabytes, and demanding - workloads:</emphasis> Proven reliability, performance, and - scalability - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">High availability:</emphasis> Cluster - support, standby configuration, hot standby configuration - </para> - </listitem> - - </itemizedlist> - </para> - - </section> - - <section id="maxdb-mysql-differences"> - - <title id='title-maxdb-mysql-differences'>&title-maxdb-mysql-differences;</title> - - <para> - The following list provides a short summary of the main - differences between MaxDB and MySQL; it is not complete. - </para> - - <itemizedlist> - - <listitem> - <para> - MaxDB runs as a client/server system. MySQL can run as a - client/server system or as an embedded system. - </para> - </listitem> - - <listitem> - <para> - MaxDB might not run on all platforms supported by MySQL. For - example, MaxDB does not run on IBM's OS/2. - </para> - </listitem> - - <listitem> - <para> - MaxDB uses a proprietary network protocol for client/server - communication. MySQL uses TCP/IP (with or without SSL - encryption), sockets (under Unix-like systems), or named pipes - (under Windows NT-family systems). - </para> - </listitem> - - <listitem> - <para> - 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 are - also implemented in MySQL 5.0. MaxDB contains a debugger for - stored procedure languages, can cascade nested triggers, and - supports multiple triggers per action and row. - </para> - </listitem> - - <listitem> - <para> - MaxDB is distributed with user interfaces that are text-based, - graphical, or Web-based. MySQL is distributed with text-based - user interfaces only; graphical user interface (MySQL Query - Browser, MySQL Administrator) are shipped separately from the - main distributions. Web-based user interfaces for MySQL are - offered by third parties. - </para> - </listitem> - - <listitem> - <para> - MaxDB supports a number of programming interfaces that also - are supported by MySQL. For developing with MaxDB, the MaxDB - ODBC Driver, SQL Database Connectivity (SQLDBC), JDBC Driver, - Perl and Python modules and a MaxDB PHP extension, which - provides access to the MySQL MaxDB databases using PHP, are - available. Third Party Programming Interfaces: Support for OLE - DB, ADO, DAO, RDO and .NET through ODBC. MaxDB supports - embedded SQL with C/C++. - </para> - </listitem> - - <listitem> - <para> - MaxDB includes administrative features that MySQL does not - have: job scheduling by time, event, and alert, and sending - messages to a database administrator on alert thresholds. - </para> - </listitem> - - </itemizedlist> - - <remark> - Maybe add table showing maxima for MaxDB and MySQL. Might be - obtained from crash-me comparison. - </remark> - - </section> - - <section id="maxdb-mysql-interoperability"> - - <title id='title-maxdb-mysql-interoperability'>&title-maxdb-mysql-interoperability;</title> - - <para> - The MaxDB Synchronization Manager was released as part of MaxDB - 7.6. The Synchronization Manager supports creation of asynchronous - replication scenarios between several MaxDB instances. However, - interoperability features also are planned, so that the - Synchronization Manager supports replication to and from a MySQL - server. - </para> - - <para> - In the first release, the Synchronization Manager supports - inserting data into MySQL. This means that initially only - replication from MaxDB to MySQL is supported. In the course of - 2005, exporting of data from a MySQL server to the Synchronization - Manager will be added, thus adding support for MySQL to MaxDB - replication scenarios. - </para> - - <para> - MaxDB 7.6, with the Synchronization Manager, was released as a - beta version in January 2005. - - <remark> - The production release is planned for April 2005. - </remark> - </para> - - </section> + <para> + MaxDB is the new name of a database management system formerly + called SAP DB. In 2003 SAP AG and MySQL AB joined a partnership and + re-branded the database system to MaxDB. The development of MaxDB + has continued since then as it was done before – through the SAP + developer team. + </para> + + <para> + MySQL AB co-operates closely with the MaxDB team at SAP around + delivering improvements to the MaxDB product. Joint efforts include + development of new native drivers to enable more efficient usage of + MaxDB in the Open Source community, and improvement of various + documentation to expand the MaxDB user base. Also interoperability + features between MySQL and MaxDB database are seen as important, + and for instance the new MaxDB Synchronization Manager supports + data synchronization from MaxDB to MySQL. + </para> + + <para> + The MaxDB database management system does not share a + common code-base with the MySQL database management system. + The MaxDB and MySQL database management systems are + independed products provided by MySQL AB. + </para> + + <para> + MySQL AB offers a complete portfolio of Professional Services + for MaxDB. + </para> - <section id="maxdb-reserved-words"> + <section id="maxdb-overview"> + <title id='title-maxdb-overview'>&title-maxdb-overview;</title> - <title id='title-maxdb-reserved-words'>&title-maxdb-reserved-words;</title> + <para> + MaxDB is a ANSI SQL-92 (entry level) compliant relational database + management system (RDBMS) from SAP AG, that is delivered by + MySQL AB as well. MaxDB fulfills the needs for enterprise usage: + safety, scalability high concurrency and performance . It runs on all + major operating systems. Over the years it has proven able to + run SAP R/3 and terabytes of data in 24x7 operation. + </para> + + <para> + The database development started in 1977 as a research project at the + Technical University of Berlin . In the early 80s it became a database + product that subsequently was owned by Nixdorf, Siemens Nixdorf, + Software AG and today – by SAP AG. Along this line it has been + named VDN, Reflex, Supra 2, DDB/4, Entire SQL-DB-Server and + ADABAS. In 1997 SAP took over the software from software AG + and renamed it to SAP DB. Since October 2000 SAP DB sources + additionally were released as open source under the GNU + General Public License (see <xref linkend="gpl-license"/>). + </para> + + <para> + In 2003 SAP AG and MySQL AB joined a partnership and re-branded + the database system to MaxDB. + </para> + + </section> + + <section id="maxdb-history"> + + <title id='title-maxdb-history'>&title-maxdb-history;</title> + + <para> + The history of MaxDB goes back to SAP DB, SAP AG's DBMS, i.e. + MaxDB is a re-branded and enhanced version of SAP DB. For many + years, MaxDB has been used for small, medium, and large installations + of the mySAP Business Suite and other demanding SQL applications + requiring an enterprise-class DBMS with regard to the number + of users, the transactional workload, and the size of the database. + </para> + + <para> + SAP DB was meant to provide an alternative to third-party database + systems such as Oracle, Microsoft SQL Server, and DB2 by IBM. In + October 2000, SAP AG released SAP DB under the GNU GPL license + (see <xref linkend="gpl-license"/>), thus making it open source + software. + </para> + + <para> + Today, MaxDB is used in about 3,500 SAP customer installations + worldwide. Moreover, the majority of all DBMS installations on Unix + and Linux within SAP’s IT department rely on MaxDB. MaxDB is + tuned towards heavy-duty online transaction processing (OLTP) + with several thousand users and database sizes ranging from + several hundred GB to multiple TB. + </para> + + <para> + In 2003 SAP and MySQL concluded a partnership and development + cooperation agreement. As a result, SAP's database system SAP DB + has been delivered under the name of MaxDB by MySQL since the + release of version 7.5 (November 2003). + </para> + + <para> + Version 7.5 of MaxDB is a direct advancement of the SAP DB 7.4 + code base. Therefore, the MaxDB software version 7.5 can be used + as a direct upgrade of previous SAP DB versions starting 7.2.04 + and higher. + </para> + + <para> + Now, as before, the former SAP DB development team at SAP AG is + responsible for developing and supporting MaxDB. MySQL AB + co-operates closely with the MaxDB team at SAP around + delivering improvements to the MaxDB product, see + <xref linkend="maxdb"/>. Both SAP AG and + MySQL AB handle the sale and distribution of MaxDB. The + advancement of MaxDB and the MySQL Server leverages synergies that + benefit both product lines. + </para> + + <para> + MaxDB is subjected to SAP AG's complete quality assurance process + before it is shipped with SAP solutions or provided as a download + from the MySQL site. + </para> + + </section> + + <section id="maxdb-features"> + + <title id='title-maxdb-features'>&title-maxdb-features;</title> + + <para> + MaxDB is a heavy-duty, SAP-certified open source database for + OLTP and OLAP usage which offers high reliability, availability, + scalability and a very comprehensive feature set. It is targetted for + large mySAP Business Suite environments and other applications + that require maximum enterprise-level database functionality and + complements the MySQL database server. + </para> + + <para> + MaxDB operates as a client/server product. It was developed to + meet the needs of installations in OLTP and Data + Warehouse/OLAP/Decision Support scenarios. + <emphasis role="bold">Benefits:</emphasis> + + <itemizedlist> + + <listitem> + <para> + <emphasis role="bold">Easy configuration and + administration:</emphasis> GUI-based Installation Manager + and Database Manager as single admin tools for DBMS + operations + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Around-the-clock operation, no planned + downtimes, no permanent attendance required:</emphasis> + Automatic space management, no need for reorganizations + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Elaborate backup and restore + capabilities:</emphasis> Online and incremental backups, + recovery wizard to guide you through the recovery scenario + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">Supports large number of users, + database sizes in the terabytes, and demanding + workloads:</emphasis> Proven reliability, performance, and + scalability + </para> + </listitem> + + <listitem> + <para> + <emphasis role="bold">High availability:</emphasis> Cluster + support, standby configuration, hot standby configuration + </para> + </listitem> + + </itemizedlist> + </para> + + </section> + + + <section id="maxdb-licensing"> + + <title id='title-maxdb-licensing'>&title-maxdb-licensing;</title> + + <para> + MaxDB can be used under the same licenses available for the other + products distributed by MySQL AB. Thus, MaxDB is available under + the GNU General Public License, and a commercial license. For more + information on licensing, see + <ulink url="http://www.mysql.com/company/legal/licensing/"/>. + </para> + + <para> + MySQL AB offers MaxDB technical support to non-SAP customers. + The MaxDB support is available on various levels (Basic, Silver and + Gold), which expand from unlimited email/web-support to 24x7 + phone support for business critical systems. + </para> + + <para> + MySQL AB also offers Licenses and Support for MaxDB when used + with SAP Applications, like SAP NetWeaver and mySAP Business + Suite. + <ulink url="http://www.mysql.com/company/contact/">Please contact</ulink> + MySQL AB for more information on licenses and support for your needs. + </para> + + <para> + Consulting and training services are available. MySQL gives classes on + MaxDB in regular intervals, see <ulink url="http://www.mysql.com/training/" /> + for a list of classes. + </para> + + </section> + + + <section id="maxdb-mysql-differences"> + + <title id='title-maxdb-mysql-differences'>&title-maxdb-mysql-differences;</title> + + <para> + MaxDB is MySQL AB's SAP-certified database. The MaxDB database server + complements the MySQL AB product portfolio. Some MaxDB features are not + availabe on the MySQL database management server and vice versa. + </para> + + <para> + The following list provides a short summary of the main + differences between MaxDB and MySQL; it is not complete. + </para> + + <itemizedlist> + + <listitem> + <para> + MaxDB runs as a client/server system. MySQL can run as a + client/server system or as an embedded system. + </para> + </listitem> + + <listitem> + <para> + MaxDB might not run on all platforms supported by MySQL. For + example, MaxDB does not run on IBM's OS/2. + </para> + </listitem> + + <listitem> + <para> + MaxDB uses a proprietary network protocol for client/server + communication. MySQL uses either TCP/IP (with or without SSL + encryption), sockets (under Unix-like systems), or named pipes + (under Windows NT-family systems). + </para> + </listitem> + + <listitem> + <para> + 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. + </para> + </listitem> + + <listitem> + <para> + MaxDB is distributed with user interfaces that are text-based, + graphical, or Web-based. MySQL is distributed with text-based + user interfaces only; graphical user interface (MySQL Control + Center, MySQL Administrator) are shipped separately from the + main distributions. Web-based user interfaces for MySQL are + offered by third parties. + </para> + </listitem> + + <listitem> + <para> + MaxDB supports a number of programming interfaces that also + are supported by MySQL. For developing with MaxDB, the MaxDB + ODBC Driver, SQL Database Connectivity (SQLDBC), JDBC Driver, + Perl and Python modules and a MaxDB PHP extension, which + provides access to the MySQL MaxDB databases using PHP, are + available. Third Party Programming Interfaces: Support for OLE + DB, ADO, DAO, RDO and .NET through ODBC. MaxDB supports + embedded SQL with C/C++. + </para> + </listitem> + + <listitem> + <para> + MaxDB includes administrative features that MySQL does not + have: job scheduling by time, event, and alert, and sending + messages to a database administrator on alert thresholds. + </para> + </listitem> + + </itemizedlist> + + <!-- Maybe add table showing maxima for MaxDB and MySQL. Might be obtained from crash-me comparison. --> + + </section> + + + <section id="maxdb-mysql-interoperability"> + + <title id='title-maxdb-mysql-interoperability'>&title-maxdb-mysql-interoperability;</title> + + <para> + MaxDB and MySQL are independed database management servers. + The interoperation of the systems is possible in a way that the systems can + exchange their data. To exchange data between MaxDB and MySQL + you can use the im- and export tools of the systems or the + MaxDB Synchronization Manager. The im- and export tools can be used to + transfer data in a in-frequently, manual fashion. The MaxDB Sychronization + Manager offers faster, automatic data transfer capabilities. + </para> + + <para> + The MaxDB Loader can be used to export data and object definitions. + The Loader can export data using MaxDB internal, binary formats and + text formats (CSV). Data exported from MaxDB in text formats can be + re-imported to MySQL using the <command>mysqldump</command> + database backup program. In order to import MySQL data into + MaxDB you can either use <command>mysqldump</command> + to create <literal>INSERT</literal> statements or + <literal>SELECT ... INTO OUTFILE</literal> to create a + text file (CSV). Use the MaxDB Loader to load the data files + generated by MySQL. + </para> + + <para> + Object definitions can be exchanged between the systems + using MaxDB Loader and the MySQL tool <command>mysqldump</command>. + As the SQL dialects of both systems differ slightly and MaxDB + has features currently not supported by MySQL like SQL constraints, + we recommend to hand-tune the definition files. + The <command>mysqldump</command> tool offers an option + <literal>--compatible-name = maxdb</literal> to produce output that is + compatible to MaxDB to make porting easier. + </para> + + <para> + As part of MaxDB 7.6, the MaxDB Synchronization Manager is + released. The Synchronization Manager supports creation of + asynchronous replication scenarios between several MaxDB + instances. However, interoperability features also are planned, so + that the Synchronization Manager supports replication to and from + a MySQL server. + </para> + + <para> + In the first release, the Synchronization Manager supports + inserting data into MySQL. This means that initially only + replication from MaxDB to MySQL is supported. In the course of + 2005, exporting of data from a MySQL server to the Synchronization + Manager will be added, thus adding support for MySQL to MaxDB + replication scenarios. + </para> + + </section> + + <section id="maxdb-links"> + + <title id='title-maxdb-links'>&title-maxdb-links;</title> + + <para> + The main page for information about MaxDB is + <ulink url="http://www.mysql.com/products/maxdb"/>. + The page gives details about the features of the MaxDB database + management systems and has pointers to documentation available. + </para> + + <para> + The MySQL Reference Manaul does not contain any MaxDB + documentation but the introduction given in this section. + MaxDB has it's own documentation, called the MaxDB library. + The MaxDB library is available on + <ulink url="http://dev.mysql.com/doc/maxdb/index.html" />. + </para> + + <para> + MySQL AB runs a community mailinglist on MaxDB, + see <ulink url="http://lists.mysql.com/maxdb" />. The list shows a vivid + community discussion. Many of the core developers + contribute to it. Product announcements are send to list. + </para> + + <para> + A web forum on MaxDB is on <ulink url="http://forums.mysql.com/" />. + The forum is for questions on MaxDB not related to SAP application. + </para> - <para> - Like MySQL, MaxDB has a number of reserved words that have special - meanings. Normally, they cannot be used as names of identifiers, - such as database or table names. The following table lists - reserved words in MaxDB, indicates the context in which those - words are used, and indicates whether or not they have - counterparts in MySQL. If such a counterpart exists, the meaning - in MySQL might be identical or differing in some aspects. The main - purpose is to list in which respects MaxDB differs from MySQL; - therefore, this list is not complete. - </para> - - <para> - For the list of reserved words in MySQL, see - <xref linkend="reserved-words"/>. - </para> - - <informaltable> - <tgroup cols="3"> - <colspec colwidth="20*"/> - <colspec colwidth="30*"/> - <colspec colwidth="50*"/> - <tbody> - <row> - <entry><emphasis role="bold">Reserved in MaxDB</emphasis></entry> - <entry><emphasis role="bold">Context of usage in MaxDB</emphasis></entry> - <entry><emphasis role="bold">MySQL counterpart</emphasis></entry> - </row> - <row> - <entry><literal>@</literal></entry> - <entry>Can prefix identifier, like <quote>@table</quote></entry> - <entry>Not allowed</entry> - </row> - <row> - <entry><literal>ADDDATE()</literal></entry> - <entry>SQL function</entry> - <entry><literal>ADDDATE()</literal>; added in MySQL 4.1.1</entry> - </row> - <row> - <entry><literal>ADDTIME()</literal></entry> - <entry>SQL function</entry> - <entry><literal>ADDTIME()</literal>; added in MySQL 4.1.1</entry> - </row> - <row> - <entry><literal>ALPHA</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>ARRAY</literal></entry> - <entry>Data type</entry> - <entry>Not implemented</entry> - </row> - <row> - <entry><literal>ASCII()</literal></entry> - <entry>SQL function</entry> - <entry><literal>ASCII()</literal>, but implemented with a different meaning</entry> - </row> - <row> - <entry><literal>AUTOCOMMIT</literal></entry> - <entry>Transactions; <literal>ON</literal> by default</entry> - <entry>Transactions; <literal>OFF</literal> by default</entry> - </row> - <row> - <entry><literal>BOOLEAN</literal></entry> - <entry>Column types; <literal>BOOLEAN</literal> accepts as values only - <literal>TRUE</literal>, <literal>FALSE</literal>, and - <literal>NULL</literal></entry> - <entry><literal>BOOLEAN</literal> was added in MySQL 4.1.0; it is a synonym for - <literal>BOOL</literal> which is mapped to - <literal>TINYINT(1)</literal>. It accepts integer values - in the same range as <literal>TINYINT</literal> as well as - <literal>NULL</literal>. <literal>TRUE</literal> and - <literal>FALSE</literal> can be used as aliases for - <literal>1</literal> and <literal>0</literal>.</entry> - </row> - <row> - <entry><literal>CHECK</literal></entry> - <entry><literal>CHECK TABLE</literal></entry> - <entry><literal>CHECK TABLE</literal>; similar, but not identical usage</entry> - </row> - <row> - <entry><literal>COLUMN</literal></entry> - <entry>Column types</entry> - <entry><literal>COLUMN</literal>; noise word</entry> - </row> - <row> - <entry><literal>CHAR()</literal></entry> - <entry>SQL function</entry> - <entry><literal>CHAR()</literal>; identical syntax; similar, not identical - usage</entry> - </row> - <row> - <entry><literal>COMMIT</literal></entry> - <entry>Implicit commits of transactions happen when data definition statements - are issued</entry> - <entry>Implicit commits of transactions happen when data definition statements - are issued, and also with a number of other statements</entry> - </row> - <row> - <entry><literal>COSH()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>COT()</literal></entry> - <entry>SQL function</entry> - <entry><literal>COT()</literal>; identical syntax and implementation</entry> - </row> - <row> - <entry><literal>CREATE</literal></entry> - <entry>SQL, data definition language</entry> - <entry><literal>CREATE</literal></entry> - </row> - <row> - <entry><literal>DATABASE</literal></entry> - <entry>SQL function</entry> - <entry><literal>DATABASE()</literal>; <literal>DATABASE</literal> is used in a - different context; for example, <literal>CREATE - DATABASE</literal></entry> - </row> - <row> - <entry><literal>DATE()</literal></entry> - <entry>SQL function</entry> - <entry><literal>CURRENT_DATE</literal></entry> - </row> - <row> - <entry><literal>DATEDIFF()</literal></entry> - <entry>SQL function</entry> - <entry><literal>DATEDIFF()</literal>; added in MySQL 4.1.1</entry> - </row> - <row> - <entry><literal>DAY()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>DAYOFWEEK()</literal></entry> - <entry>SQL function</entry> - <entry><literal>DAYOFWEEK()</literal>; by default, <literal>1</literal> - represents Monday in MaxDB and Sunday in MySQL</entry> - </row> - <row> - <entry><literal>DISTINCT</literal></entry> - <entry>SQL functions <literal>AVG</literal>, <literal>MAX</literal>, - <literal>MIN</literal>, <literal>SUM</literal></entry> - <entry><literal>DISTINCT</literal>; but used in a different context: - <literal>SELECT DISTINCT</literal></entry> - </row> - <row> - <entry><literal>DROP</literal></entry> - <entry><literal>DROP INDEX</literal>, for example</entry> - <entry><literal>DROP INDEX</literal>; similar, but not identical usage</entry> - </row> - <row> - <entry><literal>EBCDIC()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>EXPAND()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>EXPLAIN</literal></entry> - <entry>Optimization</entry> - <entry><literal>EXPLAIN</literal>; similar, but not identical usage</entry> - </row> - <row> - <entry><literal>FIXED()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>FLOAT()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>HEX()</literal></entry> - <entry>SQL function</entry> - <entry><literal>HEX()</literal>; similar, but not identical usage</entry> - </row> - <row> - <entry><literal>INDEX()</literal></entry> - <entry>SQL function</entry> - <entry><literal>INSTR()</literal> or <literal>LOCATE()</literal>; similar, but - not identical syntaxes and meanings</entry> - </row> - <row> - <entry><literal>INDEX</literal></entry> - <entry><literal>USE INDEX</literal>, <literal>IGNORE INDEX</literal> and - similar hints are used right after - <literal>SELECT</literal>; for example, <literal>SELECT - ... USE INDEX</literal></entry> - <entry><literal>USE INDEX</literal>, <literal>IGNORE INDEX</literal> and - similar hints are used in the <literal>FROM</literal> - clause of a <literal>SELECT</literal> query; for example, - in <literal>SELECT ... FROM ... USE INDEX</literal></entry> - </row> - <row> - <entry><literal>INITCAP()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>LENGTH()</literal></entry> - <entry>SQL function</entry> - <entry><literal>LENGTH()</literal>; identical syntax, but slightly different - implementation</entry> - </row> - <row> - <entry><literal>LFILL()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>LIKE</literal></entry> - <entry>Comparisons</entry> - <entry><literal>LIKE</literal>; but the extended <literal>LIKE</literal> MaxDB - provides rather resembles the MySQL - <literal>REGEX</literal></entry> - </row> - <row> - <entry><literal>LIKE</literal> wildcards</entry> - <entry>MaxDB supports <quote>%</quote>, <quote>_</quote>, - <quote>Control-underline</quote>, <quote>Control-up - arrow</quote>, <quote>*</quote>, and <quote>?</quote> as - wildcards in <literal>LIKE</literal> comparisons</entry> - <entry>MySQL supports <quote>%</quote>, and <quote>_</quote> as wildcards in - <literal>LIKE</literal> comparisons</entry> - </row> - <row> - <entry><literal>LPAD()</literal></entry> - <entry>SQL function</entry> - <entry><literal>LPAD()</literal>; slightly different implementation</entry> - </row> - <row> - <entry><literal>LTRIM()</literal></entry> - <entry>SQL function</entry> - <entry><literal>LTRIM()</literal>; slightly different implementation</entry> - </row> - <row> - <entry><literal>MAKEDATE()</literal></entry> - <entry>SQL function</entry> - <entry><literal>MAKEDATE()</literal>; added in MySQL 4.1.1</entry> - </row> - <row> - <entry><literal>MAKETIME()</literal></entry> - <entry>SQL function</entry> - <entry><literal>MAKETIME()</literal>; added in MySQL 4.1.1</entry> - </row> - <row> - <entry><literal>MAPCHAR()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>MICROSECOND()</literal></entry> - <entry>SQL function</entry> - <entry><literal>MICROSECOND()</literal>; added in MySQL 4.1.1</entry> - </row> - <row> - <entry><literal>NOROUND()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>NULL</literal></entry> - <entry>Column types; comparisons</entry> - <entry><literal>NULL</literal>; MaxDB supports special <literal>NULL</literal> - values that are returned by arithmetic operations that - lead to an overflow or a division by zero; MySQL does not - support such special values</entry> - </row> - <row> - <entry><literal>PI</literal></entry> - <entry>SQL function</entry> - <entry><literal>PI()</literal>; identical syntax and implementation, but - parentheses are mandatory in MySQL</entry> - </row> - <row> - <entry><literal>REF</literal></entry> - <entry>Data type</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>RFILL()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>ROWNO</literal></entry> - <entry>Predicate in <literal>WHERE</literal> clause</entry> - <entry>Similar to <literal>LIMIT</literal> clause</entry> - </row> - <row> - <entry><literal>RPAD()</literal></entry> - <entry>SQL function</entry> - <entry><literal>RPAD()</literal>; slightly different implementation</entry> - </row> - <row> - <entry><literal>RTRIM()</literal></entry> - <entry>SQL function</entry> - <entry><literal>RTRIM()</literal>; slightly different implementation</entry> - </row> - <row> - <entry><literal>SEQUENCE</literal></entry> - <entry><literal>CREATE SEQUENCE</literal>, <literal>DROP SEQUENCE</literal></entry> - <entry><literal>AUTO_INCREMENT</literal>; similar concept, but different - implementation</entry> - </row> - <row> - <entry><literal>SINH()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>SOUNDS()</literal></entry> - <entry>SQL function</entry> - <entry><literal>SOUNDEX()</literal>; slightly different syntax</entry> - </row> - <row> - <entry><literal>STATISTICS</literal></entry> - <entry><literal>UPDATE STATISTICS</literal></entry> - <entry><literal>ANALYZE TABLE</literal>; similar concept, but different - implementation</entry> - </row> - <row> - <entry><literal>SUBSTR()</literal></entry> - <entry>SQL function</entry> - <entry><literal>SUBSTRING()</literal>; slightly different implementation</entry> - </row> - <row> - <entry><literal>SUBTIME()</literal></entry> - <entry>SQL function</entry> - <entry><literal>SUBTIME()</literal>; added in MySQL 4.1.1</entry> - </row> - <row> - <entry><literal>SYNONYM</literal></entry> - <entry>Data definition language: <literal>CREATE [PUBLIC] SYNONYM</literal>, - <literal>RENAME SYNONYM</literal>, <literal>DROP - SYNONYM</literal></entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>TANH()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>TIME()</literal></entry> - <entry>SQL function</entry> - <entry><literal>CURRENT_TIME</literal></entry> - </row> - <row> - <entry><literal>TIMEDIFF()</literal></entry> - <entry>SQL function</entry> - <entry><literal>TIMEDIFF()</literal>; added in MySQL 4.1.1</entry> - </row> - <row> - <entry><literal>TIMESTAMP()</literal></entry> - <entry>SQL function</entry> - <entry><literal>TIMESTAMP()</literal>; added in MySQL 4.1.1</entry> - </row> - <row> - <entry><literal>TIMESTAMP()</literal> as argument to - <literal>DAYOFMONTH()</literal> and - <literal>DAYOFYEAR()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>TIMEZONE()</literal></entry> - <entry>SQL function</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>TRANSACTION()</literal></entry> - <entry>Returns the ID of the current transaction</entry> - <entry>Nothing comparable</entry> - </row> - <row> - <entry><literal>TRANSLATE()</literal></entry> - <entry>SQL function</entry> - <entry><literal>REPLACE()</literal>; identical syntax and implementation</entry> - </row> - <row> - <entry><literal>TRIM()</literal></entry> - <entry>SQL function</entry> - <entry><literal>TRIM()</literal>; slightly different implementation</entry> - </row> - <row> - <entry><literal>TRUNC()</literal></entry> - <entry>SQL function</entry> - <entry><literal>TRUNCATE()</literal>; slightly different syntax and - implementation</entry> - </row> - <row> - <entry><literal>USE</literal></entry> - <entry>Switches to a new database instance; terminates the connection to the - current database instance; all subsequent commands are - referred to this database instance</entry> - <entry><literal>USE</literal>; identical syntax, but does not terminate the - connection to the current database</entry> - </row> - <row> - <entry><literal>USER</literal></entry> - <entry>SQL function</entry> - <entry><literal>USER()</literal>; identical syntax, but slightly different - implementation, and parentheses are mandatory in MySQL</entry> - </row> - <row> - <entry><literal>UTC_DIFF()</literal></entry> - <entry>SQL function</entry> - <entry><literal>UTC_DATE()</literal>; provides a means to calculate the same - result as <literal>UTC_DIFF()</literal></entry> - </row> - <row> - <entry><literal>VALUE()</literal></entry> - <entry>SQL function, alias for <literal>COALESCE()</literal></entry> - <entry><literal>COALESCE()</literal>; identical syntax and implementation</entry> - </row> - <row> - <entry><literal>VARIANCE()</literal></entry> - <entry>SQL function</entry> - <entry><literal>VARIANCE()</literal>; added in MySQL 4.1.0</entry> - </row> - <row> - <entry><literal>WEEKOFYEAR()</literal></entry> - <entry>SQL function</entry> - <entry><literal>WEEKOFYEAR()</literal>; added in MySQL 4.1.1</entry> - </row> - </tbody> - </tgroup> - </informaltable> + </section> </section> - -</section> --- 1.26/refman-common/titles.ent 2005-08-31 18:15:22 +02:00 +++ 1.27/refman-common/titles.ent 2005-09-06 17:10:53 +02:00 @@ -590,11 +590,13 @@ <!ENTITY title-mathematical-functions "Mathematical Functions"> <!ENTITY title-maxdb "Overview of the MaxDB Database Management System"> <!ENTITY title-maxdb-basics "Basic Concepts of MaxDB"> +<!ENTITY title-maxdb-features "Features of MaxDB"> <!ENTITY title-maxdb-history "History of MaxDB"> <!ENTITY title-maxdb-licensing "Licensing and Support"> <!ENTITY title-maxdb-links "MaxDB-Related Links"> <!ENTITY title-maxdb-mysql-differences "Feature Differences Between MaxDB and MySQL"> <!ENTITY title-maxdb-mysql-interoperability "Interoperability Features Between MaxDB and MySQL"> +<!ENTITY title-maxdb-overview "Overview of the MaxDB Database Management System"> <!ENTITY title-maxdb-reserved-words "Reserved Words in MaxDB"> <!ENTITY title-memory-storage-engine "The <literal>MEMORY</literal> (<literal>HEAP</literal>) Storage Engine"> <!ENTITY title-memory-use "How MySQL Uses Memory">
| Thread | ||
|---|---|---|
| • bk commit - mysqldoc@docsrva tree (stefan:1.3484) | stefan | 6 Sep |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.916 sec. using MySQL 5.1.14-beta-log