setting up root account

Okay it appears my mysql database is simply screwed up. I am attempting to rebuild the root account and privileges and now I cant do anything. How do I rebuild the root account with proper privileges and the grant option. I am thinking: mysql -u root use mysql; GRANT ALL PRIVILEG

RE: index, unique index question

Of course, since James said he will never search for a record matching receiver_ID AND sender_ID, it would be more efficient to simply create one index for each of the columns. -Noah -Original Message- From: Kristian Myllymäki [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 14, 2007

Confused by max and group by

UES (3, 'three', 'A'); INSERT INTO `mytest` VALUES (4, 'one', 'B'); INSERT INTO `mytest` VALUES (5, 'two', 'B'); INSERT INTO `mytest` VALUES (6, 'three', 'B'); INSERT INTO `mytest` VALUES (7, 'one', '

Re: Computing Age for Select Query

here actually is a getAge function), as I am to figuring out the proper/elegant way to use them. Many thanks for any help or gentle shove(s) in the right direction. Noah -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Computing Age for Select Query

time functions of MySQL (unless there actually is a getAge function), as I am to figuring out the proper/elegant way to use them. Many thanks for any help or gentle shove(s) in the right direction. Noah

Help with Database structure..

I need some help with a database design question: To summarize our design (I'll spare you a lot of the details.) We collect text files from 20,000 different sources every day. The actual file is stored as a text file. Each source has its own table which contains a list of the text files, dat

maximum keyfile length significantly less than 8TB?

The mysql manual claims that MyISAM is essentially limited only by the filesystem for how large tables can be. Yesterday, inserts to one of my tables began failing with error 136 (keyfile full) although the file is only around 17 gigabytes. There appears to be some undocumented limitation that f

Opens MYI but not ISM files

take up over 150 Gigs of space. This would be a painfully slow conversion. >How-To-Repeat: See above >Fix: See above >Submitter-Id: Noah Silverman >Originator:AllResearch >Organization: >MySQL support: extended email support CONTRACT 725 >Synopsis:

Re: problems migrating from mysql 3.22.22 to 3.23.32

ot;/"major new features of 3.23"/"complete change list of 3.23" etc pages and never saw this mentioned. Either I'm blind/obtuse (always possible) or this was extremely under-a d v e r t i s ed. Now I get to comb through a few hundred lines of Perl code looking for

problems migrating from mysql 3.22.22 to 3.23.32

2.tar.gz), compiled and running on the old system (a dual PPro system running a heavily modified RedHat 5.1). The result are the same in either case. Thanks, Noah Romer - Before posting, please check: http://www.mysql.com/man