Hello.
MySQL 3.xx is almost out of support now. Even no bugs fixed in 3.23 (only very critical ones). General reasons about old software and it's problems can be used in your dialog with hosting provider. Usually providers leave servers with MySQL 3.xx in use and provide a new one with MySQL 4.1. Clients port their applications to the new server by themselves (if they want it, of course). > > <grin> it get worse ..... most of my commercial work is running on > servers with ver 3.23.X (sun and RH servers). I enjoy a > great relationship with my domain hoster (who is also a > programmer who uses mysql a lot), but he has been very > cautious about upgrading any of his servers, being > concerned about code breaking, etc. > > What argument might be provided to him to upgrade and what caveats > might be cited? > > Thanks very much for the pointer to the docs. > regards > tim > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
