Re: Duplicate entry error

2005-07-04 Thread Gleb Paharenko
Hello. | 4.0.17-standard | It is an old version of MySQL which could contain lots of bugs. It is strongly recommended to upgrade to the latest release 4.1.12, or if it is impossible in your production environment to 4.0.24. Usually upgrade solves such kind of errors. Please, next

Re: Post-Installation Procedures for Slackware

2005-07-04 Thread Gleb Paharenko
Hello. It depends on which distribution you've installed. General tips are contained in: http://dev.mysql.com/doc/mysql/en/unix-post-installation.html 4.0.20 is rather old, use the latest release (4.1.12). Tim Johnson [EMAIL PROTECTED] wrote: Hello All: I am most familiar

Re: Help needed regarding MySQL-C Libraries on Linux....

2005-07-04 Thread Gleb Paharenko
Hello. This is an output of diff user.c user.cpp. Which successfully compiles on my FC3 system using the following command: g++ user.cpp -I/usr/include/mysql -lmysqlclient I've changed the extension to 'cpp', so g++ could work with this file. Also #includeconio.h was commented, and

missing ibd files on upgrade of mysql from 4.1.9 to 4.1.12a

2005-07-04 Thread Jason Pyeron
I just lost a bunch of personal and work development projects whilst upgrading to MySQL 4.1.12a (msi script). I get errors like: ERROR 1016 (HY000): Can't open file: 'files.ibd' (errno: 1) there are no .ibd files in any of the data directories. I do have 3 very large files at the top.

my-medium.cnf file not created

2005-07-04 Thread njackso2
Dear Sir or Madam: After installing mysql, the template files, my-small.cnf, my-medium.cnf or my-large.cnf, were not created. I uninstalled and then reinstalled mysql, but they were still not created. I am using mysql-4.0.20a-win on Windows ME. Could you please help with this problem.

Re: missing ibd files on upgrade of mysql from 4.1.9 to 4.1.12a

2005-07-04 Thread Gleb Paharenko
Hello. [EMAIL PROTECTED] gleb]$ perror 1 OS error code 1: Operation not permitted Do you run new MySQL service under different user account? Jason Pyeron [EMAIL PROTECTED] wrote: I just lost a bunch of personal and work development projects whilst upgrading to MySQL

Re: missing ibd files on upgrade of mysql from 4.1.9 to 4.1.12a

2005-07-04 Thread Jason Pyeron
No the user is still the same, there are just no innodb files. ?anymore? On Mon, 4 Jul 2005, Gleb Paharenko wrote: Hello. [EMAIL PROTECTED] gleb]$ perror 1 OS error code 1: Operation not permitted Do you run new MySQL service under different user account? Jason Pyeron [EMAIL PROTECTED]

Re: Post-Installation Procedures for Slackware

2005-07-04 Thread Tim Johnson
* Gleb Paharenko [EMAIL PROTECTED] [050704 09:03]: Hello. It depends on which distribution you've installed. General tips are contained in: http://dev.mysql.com/doc/mysql/en/unix-post-installation.html Thanks. I have read that document. But I wasn't clear as to whether or not I

GRANT and mysql.user table

2005-07-04 Thread l'[EMAIL PROTECTED]
I tried as root having GRANT ALL PRIVILEGES with GRANT OPTION to change the privilege of a user: GRANT ALL ON mydb.* TO myUser; The result of this statement is that the query is OK and 0 rows are affected. WHen I look at the mysql table holding the grants: user, the myUser row is unchanged.

Re: GRANT and mysql.user table

2005-07-04 Thread Michael Stassen
l'[EMAIL PROTECTED] wrote: I tried as root having GRANT ALL PRIVILEGES with GRANT OPTION to change the privilege of a user: GRANT ALL ON mydb.* TO myUser; The result of this statement is that the query is OK and 0 rows are affected. WHen I look at the mysql table holding the grants: user, the

timestampdiff func miscalculation (month only)

2005-07-04 Thread Travis Hillenbrand
Description: The number of months between two dates is not calculated properly by the timestampdiff function when the second date is the same month in a future year but the same day or earlier within the month. Specifically, the number of months is obtained by calculating the

Innodb crash on failed read disk

2005-07-04 Thread Ady Wicaksono
Dear All I use RedHat 9 with 2,5 Gbyte RAM, Intel(R) Xeon(TM) CPU 2.80GHz (Hyperthread), filesystem ext3 standar linux journaling filesystem. Today my DB is crash :(, here is the log. I try to : 1. shutdown MySQL, unmount harddisk partition used by MySQL innodb data file and doing fsck.ext3