My.cnf problem when upgrade from 4.01 to 4.02

Hi, I'm a new user of mysql, I was upgrade from mysql 4.01 to 4.02 in mandrake 8.2. The following options in current running my.cnf suddently not work: innodb_data_file_path = ibdata1:100M innodb_data_home_dir= /data/mysql/ innodb_log_group_home_dir = /data/mysql/

RE: MySQL/InnoDB-4.0.2 is released

Hi, I'm sorry to trouble you, I was upgrade from mysql 4.01 to 4.02 in mandrake 8.2. The following options in current running my.cnf suddently not work: innodb_data_file_path = ibdata1:100M innodb_data_home_dir= /data/mysql/ innodb_log_group_home_dir = /data/mysql

RE: Using multi-byte character set

Hi, I'm a visual foxpro programmer: -Original Message- From: ÅÇ´f¼Ù (Borus.Kung) [mailto:[EMAIL PROTECTED]] Sent: Monday, April 29, 2002 10:00 To: [EMAIL PROTECTED] Subject: Using multi-byte character set Hi, I am using double byte character set (big5) under mandrake linux

Compare with 0 is not reliable

-Original Message- From: zlab1 [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 21, 2002 13:50 To: MySQL Mailing List ([EMAIL PROTECTED]) Subject: Problem with HAVING Hi, I'm running Mysql 4.01 on mandrake 8.2 with all production data using InnoDB type. I've a f

Problem with HAVING

Hi, I'm running Mysql 4.01 on mandrake 8.2 with all production data using InnoDB type. I've a field named "dch_pri" contain some account transaction data in format of DECIMAL (14,2). When running following query: SELECT din_no, SUM(IF(tran_type = "D", dch_pri, -dch_pri)) AS dch_sum