<< 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
    118 MySQL Technical Reference for Version 4.0.3 In MySQL 4.0 we will enable symlinks by default.  Then you should instead use the skip- symlink option if you want to disable this. 2.6.2.6  Compiling MySQL Clients on Windows In your source les, you should include `windows.h' before you include `mysql.h': #if defined(_WIN32) || defined(_WIN64) #include <windows.h> #endif #include <mysql.h> You  can  either  link  your  code  with  the  dynamic  `libmysql.lib'  library,  which  is  just  a wrapper to load in `libmysql.dll' on demand, or link with the static `mysqlclient.lib' library. Note that as the mysqlclient libraries are compiled as threaded libraries, you should also compile your code to be multi-threaded! 2.6.2.7  MySQL-Windows Compared to Unix MySQL MySQL-Windows has by now proven itself to be very stable.  This version of MySQL has the same features as the corresponding Unix version with the following exceptions: Windows 95 and threads Windows 95 leaks about 200 bytes of main memory for each thread creation. Each connection in MySQL creates a new thread, so you shouldn't run mysqld for an extended time on Windows 95 if your server handles many connections! Other versions of Windows don't su er from this bug. Concurrent reads MySQL depends on the pread() and pwrite() calls to be able to mix INSERT and  SELECT.   Currently  we  use  mutexes  to  emulate  pread()/pwrite().   We will, in the long run, replace the le level interface with a virtual interface so that  we  can  use  the  readfile()/writefile()  interface  on  NT/2000/XP  to get more speed.   The current implementation limits the number of open les MySQL can use to 1024, which means that you will not be able to run as many concurrent threads on NT/2000/XP as on Unix. Blocking read MySQL uses a blocking read for each connection.  This means that:    A connection will not be disconnected automatically after 8 hours, as hap- pens with the Unix version of MySQL.    If a connection hangs, it's impossible to break it without killing MySQL.    mysqladmin kill will not work on a sleeping connection.    mysqladmin shutdown can't abort as long as there are sleeping connections. We plan to x this problem when our Windows developers have gured out a nice workaround.
     

    Customer Support CentreMySQL Reference Manual

    Web Hosting Services
    UNIX WEB HOSTING
    SUPPORT & FAQ's
    TERMS OF USE
    Domain Services
    DOMAIN REGISTRATION
    MANAGE YOUR ACCOUNT
    SUPPORT & FAQ's
    TERMS OF USE
    SITE MAP
    Home
    Hosting Plans | Domain Registration | About Us | Contact Us | Site Map
    Terms of Use | Privacy Policy | Guarantees
    Merchant Accounts

    SpiritHost - web hosting for spiritual and education sites
    SpiritHit.com - Religious and Spiritual Portal

    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