Dyntex.net Support Centre: MySQL Reference Manual p.31

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

Chapter 1: General Information 31 how to use them. You will also nd information about functionality missing from MySQL Server, and how to work around some dierences. Our goal is to not, without a very good reason, restrict MySQL Server usability for any usage. Even if we don't have the resources to do development for every possible use, we are always willing to help and oer suggestions to people who are trying to use MySQL Server in new territories. One of our main goals with the product is to continue to work toward ANSI 99 compliancy, but without sacricing speed or reliability. We are not afraid to add extensions to SQL or support for non-SQL features if this greatly increases the usability of MySQL Server for a big part of our users. (The new HANDLER interface in MySQL Server 4.0 is an example of this strategy. See Section 6.4.2 [HANDLER], page 453.) We will continue to support transactional and non-transactional databases to satisfy both heavy web/logging usage and mission-critical 24/7 usage. MySQL Server was designed from the start to work with medium size databases (10-100 million rows, or about 100 MB per table) on small computer systems. We will continue to extend MySQL Server to work even better with terabyte-size databases, as well as to make it possible to compile a reduced MySQL version that is more suitable for hand-held devices and embedded usage. The compact design of the MySQL server makes both of these directions possible without any con icts in the source tree. We are currently not targeting realtime support or clustered databases (even if you can already do a lot of things with our replication services). We don't believe that one should have native XML support in the database, but will instead add the XML support our users request from us on the client side. We think it's better to keep the main server code as \lean and clean" as possible and instead develop libraries to deal with the complexity on the client side. This is part of the strategy mentioned previously of not sacricing speed or reliability in the server. 1.7.1 What Standards Does MySQL Follow? Entry-level SQL92. ODBC levels 0-3.51. We are aiming toward supporting the full ANSI SQL99 standard, but without concessions to speed and quality of the code. 1.7.2 Running MySQL in ANSI Mode If you start mysqld with the --ansi option, the following behaviour of MySQL Server changes: || is string concatenation instead of OR. You can have any number of spaces between a function name and the `('. This forces all function names to be treated as reserved words. `"' will be an identier quote character (like the MySQL Server ``' quote character) and not a string quote character.

MySQL Reference Manual

Our Partners

SpiritHost - web hosting for spiritual and education sites
SpiritHit.com - Religious and Spiritual Portal

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide