chael Ivanyo" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, July 14, 2002 1:26 AM
Subject: Re: My.cnf problem when upgrade from 4.01 to 4.02
> Heikki,
>
> I actually upgraded from Max-3.23.51 to the 4.0.2
&
>
> The difference between 4.0 and Max-4.0 is that Max
> supports also BDB tables.
>
> Regards,
>
> Heikki
>
> - Original Message -
> From: "Michael Ivanyo" <[EMAIL PROTECTED]>
> Newsgroups: mailing.database.mysql
> Sent: Saturday, J
g.database.mysql
Sent: Saturday, July 13, 2002 7:23 AM
Subject: Re: My.cnf problem when upgrade from 4.01 to 4.02
> Hello,
>
> I've experienced what seems to be the same problem on
> Redhat 7.2. I eventually realized that in addition to
> the regular 4.0.2 server RPM, I had to
Hello,
I've experienced what seems to be the same problem on
Redhat 7.2. I eventually realized that in addition to
the regular 4.0.2 server RPM, I had to also install
the MySql-Max 4.0.2 server RPM. After that,
everything worked fine.
I was under the impression that there would only be
one ser
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/
