<< 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
    44 MySQL Technical Reference for Version 4.0.3 The  plan  is  that  we  in  the  future  will  support  the  full  ANSI  SQL99  standard,  but  with a  lot  of  useful  extensions.   The  challenge  is  to  do  this  without  sacri cing  the  speed  or compromising the code. 1.8.1  Things That Should be in 4.0 All done.  We now only do bug xes MySQL 4.0. 1.8.2  Things That Should be in 4.1 The following features are planned for inclusion into MySQL 4.1. Note that because we have many developers that are working on di erent projects, there will also be many additional features.  There is also a small chance that some of these features will be added to MySQL 4.0.  Some of the work on MySQL 4.1 is already in progress.    Subqueries. SELECT id FROM t WHERE grp IN (SELECT grp FROM g WHERE u > 100);    New table de nition le format (`.frm' les).  This will enable us to not run out of bits when adding more table options.  One will still be able to use the old `.frm' le format with 4.0.  All newly created tables will, however, use the new format. The new le format will enable us to add new column types, more options for keys, and possibly to store and retrieve FOREIGN KEY de nitions.    SHOW COLUMNS FROM table_name  (used by  mysql  client to allow expansions of column names) should not open the table, only the de nition le. This will require less memory and be much faster.    Foreign keys for MyISAM tables, including cascading delete.    Fail-safe replication.    Replication should work with RAND() and user variables @var.    Online backup with very low performance penalty.  The online backup will make it easy to add a new replication slave without taking down the master.    Derived tables: SELECT a.col1, b.col2 FROM (SELECT MAX(col1) AS col1 FROM root_table) a, other_table b WHERE a.col1=b.col1; This could be done by automatically creating temporary tables for the derived tables for the duration of the query.    ROLLUP  and  CUBE  OLAP  (Online  Analytical  Processing)  grouping  options  for  data warehousing applications.    Allow DELETE on MyISAM tables to use the record cache.  To do this, we need to update the threads record cache when we update the `.MYD' le.    When using  SET CHARACTER SET  we should translate the whole query at once and not only strings.  This will enable users to use the translated characters in database, table, and column names.
     

    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