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

<< 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

56 MySQL Technical Reference for Version 4.0.3 MySQL Server MySQL correctly prioritises everything (AND is evaluated before OR). To get mSQL behaviour in MySQL Server, use parentheses (as shown in an example later in this section). mSQL Evaluates everything from left to right. This means that some logical calcu- lations with more than three arguments cannot be expressed in any way. It also means you must change some queries when you upgrade to MySQL Server. You do this easily by adding parentheses. Suppose you have the following mSQL query: mysql> SELECT * FROM table WHERE a=1 AND b=2 OR a=3 AND b=4; To make MySQL Server evaluate this the way that mSQL would, you must add parentheses: mysql> SELECT * FROM table WHERE (a=1 AND (b=2 OR (a=3 AND Access Control MySQL Server Has tables to store grant (permission) options per user, host, and database. See Section 4.2.6 [Privileges], page 197. mSQL Has a le `mSQL.acl' in which you can grant read/write privileges for users. 1.9.2 How MySQL Compares to PostgreSQL When reading the following, please note that both products are continually evolving. We at MySQL AB and the PostgreSQL developers are both working on making our respective databases as good as possible, so we are both a serious alternative to any commercial database. The following comparison is made by us at MySQL AB. We have tried to be as accurate and fair as possible, but although we know MySQL Server thoroughly, we don't have a full knowledge of all PostgreSQL features, so we may have got some things wrong. We will, however, correct these when they come to our attention. We would rst like to note that PostgreSQL and MySQL Server are both widely used products, but with dierent design goals, even if we are both striving toward ANSI SQL compliancy. This means that for some applications MySQL Server is more suited, while for others PostgreSQL is more suited. When choosing which database to use, you should rst check if the database's feature set satises your application. If you need raw speed, MySQL Server is probably your best choice. If you need some of the extra features that only PostgreSQL can oer, you should use PostgreSQL. 1.9.2.1 MySQL and PostgreSQL development strategies When adding things to MySQL Server we take pride to do an optimal, denite solution. The code should be so good that we shouldn't have any need to change it in the foreseeable future. We also do not like to sacrice speed for features but instead will do our utmost to

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