<< previous page   --   table of contents   --   next page >>
| | | | | | | |
  • 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
    60 MySQL Technical Reference for Version 4.0.3 If not,  one can always switch the trouble table to use one of the transactional table types.  See Section 5.3.2 [Table locking], page 355.    With UDF (user-de ned functions) one can extend MySQL Server with both normal SQL functions and aggregates, but this is not yet as easy or as exible as in PostgreSQL. See Section 9.2 [Adding functions], page 616.    Updates that run over multiple tables are harder to do in MySQL Server.  This will, however, be xed in MySQL Server 4.0.2 with multi-table UPDATE and in MySQL Server 4.1 with subselects.  In MySQL Server 4.0 one can use multi-table deletes to delete from many tables at the same time.  See Section 6.4.6 [DELETE], page 459. PostgreSQL currently o ers the following advantages over MySQL Server: Note that because we know the MySQL road map, we have included in the following table the version when MySQL Server should support this feature.  Unfortunately we couldn't do this for previous comparisons, because we don't know the PostgreSQL roadmap. Feature MySQL version Subselects 4.1 Foreign keys 4.1 Views 5.0 Stored procedures 5.0 Triggers 5.0 Unions 4.0 Full join 4.1 Constraints 4.1 or 5.0 Cursors 4.1 or 5.0 R-trees 4.1 (for MyISAM tables) Inherited tables Not planned Extensible type system Not planned Other reasons someone may consider using PostgreSQL:    Standard usage in PostgreSQL is closer to ANSI SQL in some cases.    One can speed up PostgreSQL by coding things as stored procedures.    For geographical data, R-trees make PostgreSQL better than MySQL Server.  (note: MySQL version 4.1 will have R-trees for MyISAM tables).    The PostgreSQL optimiser can do some optimisation that the current MySQL opti- miser can't do.  Most notable is doing joins when you don't have the proper keys in place  and  doing  a  join  where  you  are  using  di erent  keys  combined  with  OR.  The MySQL benchmark suite at http://www.mysql.com/information/benchmarks.html shows  you  what  kind  of  constructs  you  should  watch  out  for  when  using  di erent databases.    PostgreSQL has a bigger team of developers that contribute to the server. Drawbacks with PostgreSQL compared to MySQL Server:    VACUUM makes PostgreSQL hard to use in a 24/7 environment.    Only transactional tables.    Much slower INSERT, DELETE, and UPDATE. For a complete list of drawbacks, you should also examine the rst table in this section.
     

    Customer Support CentreMySQL Reference Manual

    Web Hosting Services
    UNIX WEB HOSTING
    MERCHANT ACCOUNTS
    DEDICATED SERVERS
    E-COMMERCE HOSTING
    SUPPORT & FAQ's
    TERMS OF USE
    Domain Services
    DOMAIN
    REGISTRATION
    MANAGE
    YOUR ACCOUNT
    SUPPORT & FAQ's
    TERMS OF USE
    Corporate Info
    ABOUT US
    OUR NETWORK
    CONTACT US
    SITE MAP
    UNIX Web Hosting | Merchant Accounts | Dedicated Hosting | E-Commerce Hosting
    Domain Registration | About Us | Our Network | Contact Us | Site Map
    Our Partners
    Copyright © 2002 Dyntex Group, Inc. All Rights Reserved
  • 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