Re: Help - I'm completely locked out of mysql
The official answer to your problem can be found in the mysql manual. This could very well be installed on your computer, somewhere (different packaging systems put it in different places, and you may or may not have included the mysql documentation package on your system). Regardless, you can _always_ go to the Documentation section on the mysql web site. This is probably a better first place to go than searching the archives, which I assume means the mailing list archives. Still, I'm surprised you didn't find anything appropriate in the archives, since this question is asked so often. http://www.mysql.com/documentation/mysql/bychapter/manual_Problems.html#Resetting_permissions It's mysqld that requires the --skip-grant-tables option, not mysql requiring a -Skip-grant option. (That's wrong in 2 different ways.) Note that the information provided at this link is _not_ just a plug-and-play solution. It will talk about things that you may not have previous experience with. For instance, mysqld. This is the mysql server (daemon). Possibly, your computer automatically runs mysqld whenever you start it up, due to an entry in /etc/init.d/mysqld, or /etc/rc.d/init.d/mysql, or any number of other similar possibilities. (If you're using SlackWare Linux or another BSD-inspired system, there won't be an init.d directory, if I recall correctly after all these years...) Even then, the /etc/init.d/mysqld script probably doesn't have within it a reference to mysqld directly. It might invoke the safe-mysqld script, or something entirely different. You could dig a while before you finally discover the thing that does the call to mysqld. I recommend you find it just so that you understand how mysqld is called, before calling it yourself directly. Other suggestions * rather than using the kill command they mention here, you might just want to do /etc/init.d/mysqld stop (or whatever is similar, given the specifics of your system) * maybe you haven't run into the GRANT command yet -- read up on it; it's in the manual, too * don't forget FLUSH PRIVILEGES! If you don't know what this means, read up about it in the manual. Good luck... Cheers, Richard -- Richard Dice * Personal 416 841 7365 * Fax 416 841 7364 ShadNet Creator * http://shadnet.shad.ca/ * [EMAIL PROTECTED] Occasional Writer, HotWired * http://www.hotwired.com/webmonkey/ squeeze the world 'til it's small enough to join us heel to toe - jesus jones - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: surely an easy quick one
I suggest: select count(*) from table your_table_name group by team ; The MySQL documentation at www.mysql.com certainly contains good documentation regarding the group by clause within it. However, it doesn't really provide a motivation for using it... nor should it. It is documentation regarding how MySQL implements SQL and RDMS in general, and not a general SQL tutorial or reference. I suggest you look a bit further afield for this kind of material. I got started with this stuff back oh 5-6 years ago with Teach Yourself Transact-SQL in 21 Days. (I was working with MS SQL Server 6.5 at the time.) It did a pretty good job at handling this kind of topic (group by), having clause, joins, cross-tab reports, etc. (It also did views, stored procedures, batch programming... all sorts of stuff I hope MySQL has one of these days. :-) ) I'm not saying that this is the book that you should get. But if you want to increase your SQL knowledge, you should look into getting something. Cheers, Richard From: Jamie Burns [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 14, 2001 9:08 AM Subject: surely an easy quick one Hello again :o) This is surely an easy quick one but my brain wont work! I have a table (ref, name, team, seminar_ref) like: 1billsupport100 2billsupport101 3billsupport102 4ben development 201 5ben development 103 6ben development 204 7bob support 104 8bob support102 9bob support107 7pat support 102 8pat support 202 9pat support 105 I need to get a count of how many individual people are in the table, that belong to a certain group. So if I wanted to find all individual people in support the answer in this case it would be 3 (bill, bob and pat). I dont need their names, just the count. -- Richard Dice ShadNet Creator * http://shadnet.shad.ca/ * [EMAIL PROTECTED] Occasional Writer, HotWired * http://www.hotwired.com/webmonkey/ squeeze the world 'til it's small enough to join us heel to toe - jesus jones - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Please read the manual
Doug Young wrote: If I may add my 0.5c here too, the MySQL manual, like so many of its kind was obviously written by a highly skilled developer(/s) but who, like virtually all of that ilk, lacks the ability to impart knowledge to others. The MySQL manual available at www.mysql.com is terrific. It's not perfect, because nothing is, and because nothing that is meant for general-purpose use can ever be perfect for all situations. However, it's still terrific. a similar situation to that existing with most unix / linux man pages time time again we see experts going on about RTFM, however all those things do is totally confuse newbies. There are two possible assertions that you could have made in your email, and I'm not sure which one you actually did. They are: * The existing MySQL documentation is poor. * The MySQL user community (especially the newbies) would be well-served by parrallel documentation that was delivered in more of a tutorial format. If you mean the latter, then sure, I agree. Hey, why not agree? It's easy to fluff off the job of writing a tutorial into the realm of wishes and other people's work. If you mean the former, then I disagree. There's a difference between newbies being totally confused about (e.g.) some of the finer points of advanced SQL (which is forgivable), and people who are too lazy to read the documentation regarding how to reset a MySQL password they'd forgotten. (This example is my most-hated, most-often-experienced question on this list.) Cheers, Richard - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
