Re: Mysql upgrade problem 3.23 to 4.1

Hello. The password hashing mechanism was updated in MySQL 4.1 to provide better security and to reduce the risk of passwords being intercepted. Use OLD_PASSWORD() instead of PASSWORD. See: http://dev.mysql.com/doc/mysql/en/Password_hashing.html Jerry Swanson [EMAIL PROTECTED] wrote:

Mysql upgrade problem 3.23 to 4.1

I upgraded mysql mysql-3.23.58-1 to mysql4.1 In mysql-3.23 ( I have this field) password | varbinary(45) | YES | | NULL | I inserted data into this field as password('pass'). I have php script that checks if login valid. mysql-3.23 and mysql-4.1 have identical

Re: Mysql upgrade problem 3.23 to 4.1

Jerry Swanson wrote: I upgraded mysql mysql-3.23.58-1 to mysql4.1 In mysql-3.23 ( I have this field) password | varbinary(45) | YES | | NULL | I inserted data into this field as password('pass'). I have php script that checks if login valid. mysql-3.23 and

Re: Mysql upgrade problem 3.23 to 4.1

Hi Jerry, (B (B (BDid you read the documentation ? (B (BIt explains that you have to upgrade the mysql database wqith the (Bmysql_fix_privileges script. (B (B (BBest regards (B (BNils Valentin (BTokyo / Japan (B (Bhttp://www.be-known-online.com (B (B (B (B I upgraded mysql

Upgrade problem

I'm trying to move a bugzilla database from a MySql 3.23.54 - 3.23.56 database on a new machine. I have exported the database with the following mysqldump -u root -pPASSWORD --add-drop-table bugs bugs.dump.sql moved the file to the new machine and done mysql -u root -pPASSWORD bugs

mysql upgrade problem

Marek, Friday, February 22, 2002, 7:11:06 PM, you wrote: MW Hello all. MW I'm using Debian 2.4.x MW I was trying to upgrade mysql.3.22 to 23 by removing default packages and MW after debianizeing rpm's with alien I installed them with dpkg. MW After I did upgrade (as I assume ;-))) somewhere

mysql upgrade problem

Hello all. I'm using Debian 2.4.x I was trying to upgrade mysql.3.22 to 23 by removing default packages and after debianizeing rpm's with alien I installed them with dpkg. After I did upgrade (as I assume ;-))) somewhere my.cnf file disappeared Do someone know how to properly upgrade 22 to 23

Upgrade problem from 3.22.27-2 - 3.23.37-8

Hi, I have the following problem: I had to install a complete new server with Suse 7.2 (MySql: 3.23.37-8). From the the old installation I only got the backup files (created with 'mysqldump database my_databases.sql') and the the database file (ISD, ISM, frm). My problem is: I can't read the

Upgrade problem from 3.22.27-2 - 3.23.37-8

Hi, I have the following problem: I had to install a complete new server with Suse 7.2 (MySql: 3.23.37-8). From the the old installation I only got the backup files (created with 'mysqldump database my_databases.sql') and the the database file (ISD, ISM, frm). My problem is: I can't read the

Upgrade Problem

Hi, I have the following problem: I had to install a complete new server with Suse 7.2 (MySql: 3.23.37-8). From the the old installation I only got the backup files (created with 'mysqldump database my_databases.sql') and the the database file (ISD, ISM, frm). My problem is: I can't read the

Upgrade Problem (Mysqlbug)

I am trying to upgrade from mysql server v. 3.22.32 up to v. 3.23.47 on my RedHat6.2 box. When I try rpm -Uhv MySQL. , I get:: Preparing...##[100%] file /usr/bin/mysqlbug from install of MySQL-3.23.47-1 conflicts with file from package

Re: myisam upgrade problem

error 28 is "No space left on device". Hang wrote: Greetings, I am upgrading my mysql from 3.22.23b to 3.23.35 on RedHat with kernel 2.4.0. I followed the instructions on the manual for the upgrade. Every goes fine except I can't convert one table from ISAM to MYISAM. I got quite a

Re: myisam upgrade problem

Thanks! So, is there any way to calculate the approximate disk space required for the transformation from ISAM to MYISAM? Gerald Clark wrote: error 28 is "No space left on device". Hang wrote: Greetings, I am upgrading my mysql from 3.22.23b to 3.23.35 on RedHat with kernel

Re: myisam upgrade problem

Hi. On Thu, Mar 29, 2001 at 10:47:54AM +0800, [EMAIL PROTECTED] wrote: Thanks! So, is there any way to calculate the approximate disk space required for the transformation from ISAM to MYISAM? I would have assumed 330MB and don't see the reason why it should use more. Obviously I am wrong

Re: myisam upgrade problem

Alternate solution, mysqldump --add-droptable db_name table_name path/with/a/lot/of/room/table_name.sql Edit your file and change the table create clause to include TYPE = MYISAM after the column defs. Ie: CREATE TABLE table_name (column1 def, column2 def,...) TYPE = MYISAM Then: mysql dbname