<< 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 53 1.9.1.1  How to Convert mSQL Tools for MySQL According to our experience,  it doesn't take long to convert tools such as  msql-tcl  and msqljava that use the mSQL C API so that they work with the MySQL C API. The conversion procedure is: 1.   Run the shell script  msql2mysql  on the source.  This requires the  replace  program, which is distributed with MySQL Server. 2.   Compile. 3.   Fix all compiler errors. Di erences between the mSQL C API and the MySQL C API are:    MySQL Server uses a MYSQL structure as a connection type (mSQL uses an int).    mysql_connect()  takes a pointer to a  MYSQL  structure as a parameter.  It is easy to de ne one globally or to use  malloc()  to get one.   mysql_connect()  also takes two parameters for specifying the user and password.  You may set these to NULL, NULL for default use.    mysql_error()  takes the  MYSQL  structure as a parameter.  Just add the parameter to your old msql_error() code if you are porting old code.    MySQL Server returns an error number and a text error message for all errors.  mSQL returns only a text error message.    Some incompatibilities exist as a result of MySQL Server supporting multiple connec- tions to the server from the same process. 1.9.1.2  How mSQL and MySQL Client/Server Communications Protocols Di er There are enough di erences that it is impossible (or at least not easy) to support both. The most signi cant ways in which the MySQL protocol di ers from the mSQL protocol are listed here:    A message bu er may contain many result rows.    The message bu ers are dynamically enlarged if the query or the result is bigger than the current bu er, up to a con gurable server and client limit.    All packets are numbered to catch duplicated or missing packets.    All  column  values  are  sent  in  ASCII.  The  lengths  of  columns  and  rows  are  sent  in packed binary coding (1, 2, or 3 bytes).    MySQL can read in the result unbu ered (without having to store the full set in the client).    If a single read/write takes more than 30 seconds, the server closes the connection.    If a connection is idle for 8 hours, the server closes the connection.
     

    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