<< 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
    Chapter 1:  General Information 49    Change all const expressions with calculated expressions if possible.    Optimise key = expression.   At the moment only key = eld or key = constant are optimised.    Join some of the copy functions for nicer code.    Change `sql_yacc.yy' to an inline parser to reduce its size and get better error mes- sages (5 days).    Change the parser to use only one rule per di erent number of arguments in function.    Use of full calculation names in the order part (for ACCESS97).    MINUS,  INTERSECT, and  FULL OUTER JOIN.  (Currently  UNION  [in 4.0] and  LEFT OUTER JOIN are supported.)    SQL_OPTION MAX_SELECT_TIME=# to put a time limit on a query.    Make the update log write to a database.    Add to LIMIT to allow retrieval of data from the end of a result set.    Alarm around client connect/read/write functions.    Please note the changes to  safe_mysqld:  according to FSSTND (which Debian tries to  follow)  PID   les  should  go  into  `/var/run/<progname>.pid'  and  log   les  into `/var/log'.   It  would  be  nice  if  you  could  put  the  "DATADIR"  in  the   rst  decla- ration  of  "pid le"  and  "log",  so  the  placement  of  these   les  can  be  changed  with  a single statement.    Allow a client to request logging.    Add use of zlib() for gzip-ed les to LOAD DATA INFILE.    Fix sorting and grouping of BLOB columns (partly solved now).    Stored procedures.  Triggers are also being looked at.    A simple (atomic) update language that can be used to write loops and such in the MySQL server.    Change  to  use  semaphores  when  counting  threads.    One  should   rst  implement  a semaphore library to MIT-pthreads.    Don't  assign  a  new  AUTO_INCREMENT  value  when  one  sets  a  column  to  0.   Use  NULL instead.    Add full support for JOIN with parentheses.    As an alternative for one thread/connection manage a pool of threads to handle the queries.    Allow one to get more than one lock with  GET_LOCK.  When doing this, one must also handle the possible deadlocks this change will introduce. Time is given according to amount of work, not real time. 1.8.5  Things We Don't Plan To Do    Nothing; we aim toward full ANSI 92/ANSI 99 compliancy.
     

    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