Forum Moderators: phranque

Message Too Old, No Replies

Mysql - 3.23 or 4.1

is there a benefit of going to 4.1?

         

AprilS

1:58 am on Feb 18, 2004 (gmt 0)

10+ Year Member



I'm currently in the middle of configuring a new server and just curious if anyone knows of any key benefits of using MySQL 4.1 as apposed to MySQL 3.23. our server (dual xeon processors running freebsd 4.9) is currently using mysql 3.23

txbakers

2:24 am on Feb 18, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



4.1 has unions and transactions. Much better.

AprilS

2:39 am on Feb 18, 2004 (gmt 0)

10+ Year Member



Do you think 4.1 is stable enough to use in a production environment (online store)? It still says its in alpha....but it has been in alpha stage for quite a while and now they have 5.0 alpha as well. I'm just a bit confused and now wondering if 4.0 is better bet if 4.1 isn't stable.

I've been trying to read as much as possible on MySQL.com but they aren't too descriptive.

txbakers

3:45 am on Feb 18, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



4.0 will be fine, still has unions and transactions.

I've been using 3.23 for years without incident.

Can't wait to migrate to 4.0

AprilS

4:30 am on Feb 18, 2004 (gmt 0)

10+ Year Member



Thank you txbakers

I read that 4.1 allows nested select statements. This would be GREAT! I have been waiting for this feature for years with MySQL! Does anyone know of the stability of 4.1?

bcc1234

5:06 am on Feb 18, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I have been waiting for this feature for years with MySQL!

Risking to start a religious war here, but may I ask why haven't you switched to PostgreSQL?

AprilS

5:22 am on Feb 18, 2004 (gmt 0)

10+ Year Member



Well, I haven't fully looked into PostgreSQL - but mainly I haven't made the move because of the hundreds of scripts I've written that use MySQL

henry0

1:28 pm on Feb 18, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



major advantage of PEAR
switching from for ex MySQL to another DB almost on the fly
<<<
require_once 'DB.php';
// script name:db_connect.php
//require the PEAR::DB classes. named: DB.php

//list of possible DB engines:
//mysql -> MySQL
//pgsql -> PostgreSQL
//ibase -> InterBase
//msql -> Mini SQL
//mssql -> Microsoft SQL Server
//odbc -> ODBC (Open Database Connectivity
//ifx -> Informix
//fbsql -> FrontBase

$db_engine = 'mysql';
$db_user = 'root';
$db_pass = '';
$db_host = 'localhost';
$db_name = 'My_DB';

$datasource = $db_engine.'://'.
$db_user.':'.
$db_pass.'@'.
$db_host.'/'.
$db_name;

coopster

2:27 pm on Feb 18, 2004 (gmt 0)

WebmasterWorld Administrator 10+ Year Member



I've been running 4.1.1 alpha on my development machine for a bit now and the only surprise/issue I've run into was user passwords. Not from the MySQL client, mind you, that works just fine. However, when attempting connections via PHP scripts on my Apache server I received an error:

Client does not support authentication protocol error

I was able to use the workaround, but I really wouldn't want to have to go through all this in a migration yet in a production environment:

[mysql.com...]

UPDATE mysql.user SET Password = OLD_PASSWORD('[i]password[/i]') WHERE User = '[i]this_user[/i]';


Related resources:
[mysql.com...]
[mysql.com...]
[mysql.com...]