Re: Windows - logging into MySQL
Clearly you don't read instructions as well as you'd like us to think. As has been pointed out by numerous people, the instructions that were suggested to are applicable to the version of MySQL that you are running (3.2.3) I followed the link suggested to you, and it took me a whole second to discern that the instructions are applicable to 3.2.3. (Hint: look at the title of the page, namely 'MySQL 3.23, 4.0, 4.1 Reference Manual. So your entire arguement about giving this list a bad name is fallacious. You complained that people should give proper answers or shut their mouths. Well, if you had taken ANY time to really look at the FREE advice that someone kindly gave you, perhaps you'd realize that the answer is fine. Not to mention that in your complaint you end up doing the same thing that you are complaining about, namely giving yourself a bad name. I don't watch this list religiously but happened to check this thread. I will remember your name, and it will be a cold day in hell before i give you any help. Furthermore, when i read your statement of Never mind anyone responding, I'll find my own damn answers it sure implied to me that you wouldn't be back to this list, considering its horrible reputation and all. But not more than 10 minutes later, you are back posting to the list again. That really reminds me of small children saying things like I hate you, im never talking to you again and then ten minutes later are asking you for help. If you're coming to a free source for help, at least be gracious and realize that people are helping you for no gain of their own. Not to mention that EVERYONE makes mistakes, including you. You made the mistake of thinking that the answer you received didn't apply to the MySQL version that you're using. Also, if you're going to make an ultimatum (such as never returning to this list), at least stick with it. Don't come back ten minutes later. On Wednesday 30 November 2005 16:50, Beauford wrote: This is why lists like this get a bad name. First off, these instructions are for 4.1. Secondly. What makes you think I haven't read the instructions or searched extensively on Google etc. Either give a proper answer or just shut your mouth. Never mind anyone responding, I'll find my own damn answers. Thanks for the help. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: November 30, 2005 12:16 AM To: Beauford Cc: mysql@lists.mysql.com Subject: Re: Windows - logging into MySQL Beauford [EMAIL PROTECTED] wrote on 11/29/2005 11:31:24 PM: I just installed MySQL 3.23 (the only one I could get to work) and I find that I can log into the server just by typing mysql at the DOS prompt. Ho do make it so you have to use a user name and password to get in. Thanks Running on Win2k Advance Server. You could try following the installation instructions in the manual http://dev.mysql.com/doc/refman/4.1/en/windows-installation.html Shawn Green Database Administrator Unimin Corporation - Spruce Pine -- Sean Peters Senior Programmer, WIREData Inc. [EMAIL PROTECTED] The software required Windows 2000 or better, so i Downloaded Linux -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: How to add a host so 'root' can connect to the server from it
Its been a while since i've dealt much with MySQL permissions, but do you need to explicitly state 'localhost' as the machine in some circumstances. The other thing i thought of is a guess, as i don't program Java, but have had an analogous problem using Perl. It it possible that Java is dealing with the passwords using the old password scheme and the server has the passwords in the new scheme (or the other way around)? Just a couple guesses that are probably incorrect. On Thursday 03 November 2005 16:02, [EMAIL PROTECTED] wrote: Answers intermixed. See below Xiaobo Chen [EMAIL PROTECTED] wrote on 11/03/2005 04:28:08 PM: Thank so much for the detailed explaination. I do appreciate it. It's more clear now. But I still have a question: I do see 'root' after: select user,host from mysql.user; Then I did this as you said: GRANT SELECT ON mydatabase.* TO [EMAIL PROTECTED] IDENTIFIED BY 'mypassword'; then I issue: select * from mysql.user where user='root'; I found the select previlege is still 'N'. Besided this, how do I know 'mydatabase' from those tables in 'mysql' database that 'mydatabase' is allowed to be connected by 'root' from the IP. I am confusing here because the 'user' table only give the association betweem 'host' and user 'root' in the Mysql server. But where is the database association? wait a minute, yes, I see. When I issue: select * from mysql.db where user='root'; I did see the association and the SELECT_priv is 'Y' there. That's correct, the `user` table controls GLOBAL permissions. The `db` table controls database-specific permissions (there can be multiple databases on any server). But, in the java program running in the local XP machine still can NOT connect to the database existing in the other Solaris machine!! I tried in the local XP machine: telnet theserver 3306 I failed. I guess this is why I can not connect to the server. Could be it possible that the Solaris machine deny any request from the PC to the port 3306? I can ssh to the server, or using winscp. There are several possibilities here: XP is denying outbound connections to your Solaris machine (quite likely) Solaris is denying connections from your XP machine (not likely) Firewalls, routers, or proxy servers between the XP and Solaris machines are blocking the connection attempt. If you were able to connect to the MySQL server, your MySQL error would say that you could not authenticate not could not connect I am really confused here. Is it a mysql issue or the system configuration issue on the server? I think it's a system configuration issue on the XP machine. I believe the XP firewall is getting in your way. Btw, I can run the same java program from other machine in Solaris system to connect the database as the user 'root'. Does this imply that it's administration issue? Network administration, not MySQL administration (yet). Thanks for your kind help and patience. Xiaobo My pleasure! Shawn Green Database Administrator Unimin Corporation - Spruce Pine previous responses snipped -- Sean Peters Senior Programmer, WIREData Inc. [EMAIL PROTECTED] The software required Windows 2000 or better, so i Downloaded Linux -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
UUID storage (again)
The other day i asked about the proper column to store UUID's in. After thinking about it some more, i still think that a BINARY(16) is a better way to store a UUID. I'd need to strip the dashes from the formatting, but the storage would only be half as much (slightly less actually) as the suggested VARCHAR(36). The index lookups seem like they'd be faster too. Am i offbase? Also, in talking to a friend that uses that other database from redmond, i discovered that they have build in GUID (same as UUID from what i can discern) columns that are optimized for that kind of data. As it seems that UUID's are becoming the preferred internal ids, are there any plans for UUID column optimizations in MySQL? -- Sean Peters Senior Programmer, WIREData Inc. [EMAIL PROTECTED] The software required Windows 2000 or better, so i Downloaded Linux -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
UUIDs - first usage for me
Hi all, Im researching switching a production database system to use UUID's instead of AUTO_INCREMENT columns for various ids. I've looked at various MySQL documentation, and it seems to be what i want. This change will really affect 2 separate database servers. Both are using InnoDB tables. One is running MySQL 4.1.3-beta on solaris, and the other is running 4.1.8-Max on Redhat Linux. From what i've been reading, the only thing i cant determine is what column type to use to store the UUID's. These will be foreign keys between some tables, and the unique ids in all tables for this system. Should i be using BINARY() columns ? Thanks much -- Sean Peters Senior Programmer, WIREData Inc. [EMAIL PROTECTED] The software required Windows 2000 or better, so i Downloaded Linux -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Insert decimals with rounding
Hi all. I am trying to figure out if there is a way to configure MySQL so that when inserts occur on decimal fields where the value being inserted has more precision than the field specification, then the value inserted is rounded instead of truncated. For example, if i have a column: Acres DECIMAL(14,3) NOT NULL DEFAULT 0 and i'm inserting the value '1.5467' currently, the value 1.546 is inserted. But i want the behaviour to round this number to 1.547 Is this possible, or will i have to do that manually (programmatically) for all the decimal fields that i want to behave this way. Note: The application htat i need this for is driven by Perl with the DBI / DBD::MySQL Thanks much -- Sean Peters Senior Programmer, WIREData Inc. [EMAIL PROTECTED] The software required Windows 2000 or better, so i Downloaded Linux -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
data migration question
I have a table that i am modifying the schema of, and am having a particular problem with my data migration program. The old format has a column defined as: Range char(3) not null default '', which is either'' or contains a number (1 or 2 digits), and is sometimes followed by a direction (N,S,E,W) In the schema that im migrating to, the definition has changed so that there are 2 columns: Range TINYINT UNSIGNED NOT NULL DEFAULT 0, Range_Direction char(1) I have a Perl script that is doing a SELECT INTO OUTFILE on the old table, and a LOAD DATA INFILE into the new table. I havent been able to figure out a SELECT clause that will properly break up the old Range. Using a SELECT clause query like: SELECT Range REGEXP ^[0-9]+, Range REGEXP [NSEW]$ FROM ... will tell me about whether the Range column value is actually what it should be, but i was looking for a function that would give me the specific string that matched the regex, for instance using the above regexes on a range value of '32E', the first part matches '32' and the second part matches 'E'. REGEXP just gives whether the pattern matched the expression. This is very easy in Perl, is there any way to do it in MySQL? thanks much sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql_config missing - already read much docs
I just upgraded Mysql to 4.1.4-0 on linux using the following: MySQL-server-4.1.4-0.i386.rpm MySQL-client-4.1.4-0.i386.rpm So when i went to upgrade my perl DBI DBD::mysql packages, it noticed that mysql_config was missing. My understanding is that mysql_config should be installed with the client libraries. I looked at the /usr/bin directory before and after installing the client libs, and mysql_config is not there. Here is a diff output of 'ls -l /usr/bin/my *' both before and after the client rpm was installed. -rwxr-xr-x1 root root 1696220 Aug 28 02:54 mysql -rwxr-xr-x1 root root 111478 Aug 28 02:54 mysqlaccess -rwxr-xr-x1 root root 1516376 Aug 28 02:54 mysqladmin -rwxr-xr-x1 root root 1550488 Aug 28 02:54 mysqlbinlog 6a11 -rwxr-xr-x1 root root 1512908 Aug 28 02:54 mysqlcheck 10a16,17 -rwxr-xr-x1 root root 1533448 Aug 28 02:54 mysqldump -rwxr-xr-x1 root root 4986 Aug 28 02:54 mysqldumpslow 11a19 -rwxr-xr-x1 root root 2653 Aug 28 02:54 mysql_find_rows 14a23 -rwxr-xr-x1 root root 1510200 Aug 28 02:54 mysqlimport 17a27,28 -rwxr-xr-x1 root root 1510316 Aug 28 02:54 mysqlshow -rwxr-xr-x1 root root13647 Aug 28 02:54 mysql_tableinfo 19a31 -rwxr-xr-x1 root root 680464 Aug 28 02:54 mysql_waitpid So the client rpm did install a bunch of things, but not the mysql_config executable. I'm rather confused by this. Perhaps i should go back to installing source distros. Anybody seen anything like this? thanks much sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Cascade on delete question.
I have two tables, call them Parent and Child, where the records in Child have a foreign key relation to Parent, with a Cascade on Delete. If i delete records from Parent, the corresponding records in Child will be deleted. Is there any way that i can get a count of the records in Child that were deleted? without doing a 'Select count(*) FROM Child' before and after the delete? Im writing a utility that sometimes deletes records, and we'd like to know how many from each table, and i'd like to take advantage of the cascade on delete. thanks sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Simple DB design question
I have some data that is stored by the year it is related to. So I have one
table that stores the Year the data is related to, among other things. At any
given time, 1 year is considered the 'active year', and the rest are
considered inactive.
The table is something like:
CREATE TABLE Data_Info
Data_Info_IDINT,
YearINT,
...
So my question is how do i best store which year is active. 2 designs come to
mind:
1) add a column such as:
Status ENUM('Active', 'Inactive')
and adjust accordingly as the active year changes.
2) have a separate table:
CREATE TABLE Active_Data (
Data_Info_IDINT,
Key (Data_Info_ID),
FOREIGN KEY (Data_ID) References Data_Info(Data_Info_ID)
);
With design 1, i need to make sure that only 1 record is ever set as 'Active'.
With design 2, there will only ever be 1 record in the Active_Data table.
Neither idea seems very good to me.
Any suggestions?
thanks much
sean peters
[EMAIL PROTECTED]
mysql, query
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Performance question with perl DBI
Hi all, i have a MySQL driven web system that searches a pretty big DB of property info. (10 data tables, about 50,000,000 total rows, average 300 concurrent users) There are actually 2 databases that feed this site, one is meta info, and isnt hit that heavily. Lets call those DB's 'data' and 'metadata'. So my perl cgi handler creates a MySQL DBI connection to the 'data' db. When i need info from the 'metadata', i see a couple options. 1) issue query 'use metadata'. Do whatever. issue query 'use data' 2) dont change DB's, but have all queries into 'metadata' explicitly name the tables, like '... metadata.some_table...' I was wondering if either method has better performance. They seem about the same to me. Oh, im using InnoDB with the innodb_file_per_table setting. The 'data' DB is on a separate physical drive from 'metadata' Any thoughts? need more info, let me know? am i being too anal? thanks much sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Error: The table 'property' is full
When loading a new InnoDB database, I received the error: Error: The table 'property' is full I was quite surprised to get this error. When looking at the file sizes, i notieced that InnoDB tables on 4.1.3beta take up at least twice the space on the filesystem as MyISAM tables on 4.0.2 Is this normal? I am running on Solaris 5.9 This is creating a serious problem for my upgrade. I have the drive space, but i'll need to reconfigure the drives. I think that will work. Im just pretty surprised. any thoughts? thanks sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Perl DBD upgrade
Im having some difficulty with the perl DBI/DBD in conjunction with a MySQL upgrade. Here's the situation: On the DB server machine, i have MySQL 4.1.3beta running for testing upgrading, but MySQL 4.0.2 is also running (production). I can connect locally on the DB server through various clients, and have permissions as needed. But when i try to connect via a web server, i get various connect errors based on the params i pass. The error that is telling me the most is: DBI connect(...) failed: Client does not support authentication protocol requested by server; consider upgrading MySQL client at script line XXX But, i upgraded the DBI to 1.43, and the MySQL DBD to 2.9004 on both the DB server and the webserver (DB client). What im thinking the problem is: the webserver is running MySQL for other apps, and the DBD is built based on that MySQL, which is pre 4.1 series, so it doesnt understand the new MySQL auth protocols. (Note the webserver is running Perl 5.6.1) But, i didnt think that the DBD was built based on a MySQL server, because the rest of the webservers in the pool dont run MySQL, but i can still install the DBI and DBD. So im at a loss here. Can i tell the DBD to build based on the DB servers MySQL install, or does that question not even make sense? I think i need to upgrade the MySQL client libraries on the webserver, but i dont want to disturb other peoples MySQL on that box. Note: I absolutely cannot upgrade the mysql server or Perl on the webserver. Any Advice? Thank much sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Upgrading Mysql and Perl DBD
I now have MySQL 4.0.2 and MySQL 4.1.3 beta both installed and running on one machine. I want to be able to use the Perl DBI / DBD to connect to both servers. I understand that there have been some changes between the MySQL 4.0.X and 4.1.X series that may require differently compiled DBD's. So my question is, do i need to have 2 separate DBD versions, or will the newer one work for both MySQL servers. The old DBD does not work for the new server. This is demonstrated by the error message: DBI-connect(...) failed: Client does not support authentication protocol requested by server; consider upgrading MySQL client at connect_test.pl line 19 All the connect_test.pl tries to do is create a db connection to each server separately. Any insight would be greatly appreciated thanks much sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Documentation problem?
hi all. In my struggles to buildl MySQL 4.1.3deta, i read a lot of online documentation, and in the process i found a lot of info about various configure flags in writeups all over the web. One problem i encountered, that i finally figured out was that some documentation names the flag --with-extra-charsets as --with-extra-charset I finally got it right, but most of what i read omitted the (s). The configure script (quietly) allows the incorrect flag. I dont know what can be done, with so many contributors to the documentation, reviewing everything in that much detail doesnt seem wholly reasonable. I'd guess there are a myriad of similar little issues. Any thoughts on how to minimize this problem. Just wanted to bring this out. thanks sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
multiple server versions on 1 box startup error#
I am trying to run two different MySQL server versions on the same solaris machine. I already have a 4.0.2 running, and i have successfully installed 4.1.3 beta. I ran mysql_install_db successfully (after setting LD_LIBRARY_PATH), but when i try to run mysqld_safe --user=mysql I get the error: A mysqld process already exists [1]+ Exit 1 ./mysqld_safe --user=mysql This is certainly true, because my 4.0.2 is running, but i dont understand why this is a problem. I am running the mysqld_safe for version 4.1.3, and when i built 4.1.3 i used the configure options: (among others) --prefix=/usr/loca/mysql-4.1.3 --with-tcp-port=3306 --with-unix-socket-path=/tmp/mysql-4.1.3.sock --datadir=/var/mysql-4.1.3 And these options are all different from the 4.0.2 configuration. So i assumed that things would run ok. The only thing i can think of is that the /vaar/mysql-4.1.3/my.cnf is not being read correctly. Perhaps i have an error in it, but i'd think that mysqld_safe would let me know. If its not being read, then some options from my default /etc/my.cnf are not being overridden, and that could be the problem. Here is the info on the /var/mysql-4.1.3/my.cnf file: -rw-r--r-- 1 root other 2042 Aug 12 18:08 my.cnf and the permissions ownership are identical to that for /etc/my.cnf I am at a loss thanks much. sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
datadir specification, etc
I am 100% convinced that mysql 4.1.3 beta is not properly reading the my.cnf configuration files. If i remove the /etc/my.cnf file and try to start mysql 4.1.3 with (im working from /usr/local/mysql-4.1.3/bin) ./mysqld_safe i get the following output: (mccoy is the name of the machine im on) touch: /usr/local/mysql-4.1.3/var/mccoy.err cannot create chown: /usr/local/mysql-4.1.3/var/mccoy.err: No such file or directory Starting mysqld daemon with databases from /usr/local/mysql-4.1.3/var ./mysqld_safe: /usr/local/mysql-4.1.3/var/mccoy.err: cannot create If i remove the /var/mysql-4.1.3/my.cnf file, i get the same output as above, so its not being read either way. And i did specify /var/mysql-4.1.3/ as my datadir with .configure when building 4.1.3 if i put the /etc/my.cnf file back, i get the following: A mysqld process already exists So clearly, the /etc/my.cnf is being read, but the /var/mysql-4.1.3/my.cnf is not. so i guess it doesnt matter what i specify in there at this point. One strange thing is that ./msqyd_safe tries to use the databases in /usr/local/mysql-4.1.3/var/ But i specified a different datadir with configure! my configure --prefix=/usr/local/mysql-4.1.3 but why should that matter? In fact, when i installed 4.1.3 (make install), the directory /usr/local/mysql-4.1.3/var/ was NOT created. I dont think most of the info ive given matters, because my run-time configuration doesnt appear to be the problem. I dont believe that my build configuration took effect properly. Does any of this make sense? Still completely lost. thanks sean peters [EMAIL PROTECTED] *** Here's some my.cnf data, if it really matters *** Here is part of the /var/mysql-4.1.3/my.cnf file: [client] port= 3307 socket = /tmp/mysql-4.1.3.sock pid-file= /usr/local/mysql-4.1.3/mysql-4.1.3.pid datadir = /var/mysql-4.1.3/ [mysqld] port= 3307 socket = /tmp/mysql-4.1.3.sock pid-file= /usr/local/mysql-4.1.3/mysql-4.1.3.pid datadir = /var/mysql-4.1.3/ And here is info from /etc/my.cnf file: [client] port= 3306 socket = /tmp/mysql.sock [mysqld] port= 3306 socket = /tmp/mysql.sock -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB file per table directive
I've been reading (and reading...) the innodb documentation about using the innodb_file_per_table directive, and one thing still confuses me. If i use this directive, then is it correct that the setting innodb_data_file_path will specify the shared innodb information? Also, when i create databases, there will be a directory created off of datadir that will hold all the separate innodb table files for that database. I.E. when i do: Create database innodb_test; # this creates a directory [datadir]/innodb_test/ and when i issue: use database innodb_test; Create table test_1 (... )type=InnoDB; # this creates files: # [datadir]/innodb_test/test_1.frm # [datadir]/innodb_test/test_1.ibd And when i create a separate db, say innodb_test_2 then basically the same thing happens, but in directory innodb_test_2 ? What i want to do is have separate physical drives mounted in subdirectories of [datadir], so each physical disk holds separate databases. There will also be smaller DBs on the physical drive that [datadir] is on. Am i understanding all of this correctly? thanks much sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
trouble building mysql 4.1.3
I am getting an error from make test when trying to build MySQL 4.1.3 beta The error is as follows: ERROR: .../mysql-4.1.3-beta/mysql-test/var/run/master.pid was not created in 30 seconds; Aborting make: *** [test] Error 1 I read online about using the --with-extra-charset=complex with configure. (even though this is documented as fixed, ive tried without this directive also, with the same error) This runs on Solaris: SunOS [machine_name] 5.9 Generic_112233-11 sun4u sparc SUNW,Ultra-Enterprise Here is everything i did from the command line: (i am running as root - i tried as another user too) CC=gcc CFLAGS=-03 CXX=gcc CXXFLAGS=-03 felide-constructors -fno-exceptions -fno-rtti ./configure --with-low-memory --enable-assembler \ --with-extra-charset=complex --with-tcp-port=3307 \ --with-unix-socket-path=/tmp/mysql-4_1_3.sock \ --prefix=/usr/local/mysql-4.1.3 LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib; export LD_LIBRARY_PATH make make test So im at a loss. Note that i have all the nonstandard settings: port, etc. because i am trying to test this version ( tweak carious settings) on a production server without disturbing the 4.0.2 that is already running. Thanks again. sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
make test grant_cache test failing
Hi all, still building 4.1.3 I am now getting an error in make test like this: ERROR: ... At line 136: Result length mismatch (the last lines may be the most important ones) Below are the diffs between actual and expected results: --- *** r/grant_cache.resultMon Jun 28 01:26:46 2004 --- r/grant_cache.rejectTue Aug 10 23:44:49 2004 *** *** 112,119 Variable_name Value Qcache_not_cached 1 show grants for current_user(); ! Grants for @localhost ! GRANT USAGE ON *.* TO ''@'localhost' select user2; user2 user2 --- 112,119 Variable_name Value Qcache_not_cached 1 show grants for current_user(); ! Grants for [EMAIL PROTECTED] ! GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' WITH GRANT OPTION select user2; user2 user2 --- Please follow the instructions outlined at http://www.mysql.com/doc/en/Reporting_mysqltest_bugs.html to find the reason to this problem and how to report this. Aborting: grant_cache failed. To continue, re-run with '--force'. Ending Tests Shutting-down MySQL daemon Master shutdown finished Slave shutdown finished make: *** [test] Error 1 When i run: diff grant_cache.result grant_cache.reject here is the output: 115,116c115,116 Grants for @localhost GRANT USAGE ON *.* TO ''@'localhost' --- Grants for [EMAIL PROTECTED] GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' WITH GRANT OPTION This looks somewhat trivial, but i cant get beyond it to finish the test. make does not understand the --force directive, so the advice in the error wont work. thanks much, sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: make test grant_cache test failing
UPDATE: I modified the grant_cache.result file to the expected output and got past the test. It looked like the incorrect query was being issued, or in any case that make test was doing something different than what the grant_Cache.result file expected On Tuesday 10 August 2004 15:59, sean c peters wrote: Hi all, still building 4.1.3 I am now getting an error in make test like this: ERROR: ... At line 136: Result length mismatch (the last lines may be the most important ones) Below are the diffs between actual and expected results: --- *** r/grant_cache.resultMon Jun 28 01:26:46 2004 --- r/grant_cache.rejectTue Aug 10 23:44:49 2004 *** *** 112,119 Variable_name Value Qcache_not_cached 1 show grants for current_user(); ! Grants for @localhost ! GRANT USAGE ON *.* TO ''@'localhost' select user2; user2 user2 --- 112,119 Variable_name Value Qcache_not_cached 1 show grants for current_user(); ! Grants for [EMAIL PROTECTED] ! GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' WITH GRANT OPTION select user2; user2 user2 --- Please follow the instructions outlined at http://www.mysql.com/doc/en/Reporting_mysqltest_bugs.html to find the reason to this problem and how to report this. Aborting: grant_cache failed. To continue, re-run with '--force'. Ending Tests Shutting-down MySQL daemon Master shutdown finished Slave shutdown finished make: *** [test] Error 1 When i run: diff grant_cache.result grant_cache.reject here is the output: 115,116c115,116 Grants for @localhost GRANT USAGE ON *.* TO ''@'localhost' --- Grants for [EMAIL PROTECTED] GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' WITH GRANT OPTION This looks somewhat trivial, but i cant get beyond it to finish the test. make does not understand the --force directive, so the advice in the error wont work. thanks much, sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Running multiple versions of MySQL on 1 machine
Hi all, I am looking to upgrade to MySQL 4.0.13 on a Solaris production server, and would like to install and test 4.0.13 without disturbing the existing 4.0.2 server, so that there will be minimal downtime when actually upgrading the production system. So, i should be able to compile 4.0.13 without any problems, by just havnig a different base directory. But, by default, MySQL reads /etc/my.cnf at startup, so im wondering if i'll need to switch out the /etc/my.cnf files depending on which server I'm starting. Also, since client programs get options from that same file, it appears that there will be a problem running them both concurrently, because when a client connects, it will need to read the proper my.cnf, and if i have different clients connecting to each server i'd need to keep switching the files, but i cant realistically know in advance when clients are connecting to which server, so this will not work properly. Can i compile mysql with a different configuration so that it reads the default my.cnf from somewhere else, say /sandbox/etc/my.cnf for instance? Any other problems with running concurrent MySQL servers on the same machine? thanks much sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Running multiple versions of MySQL on 1 machine
I guess i dont fully understand how mysql uses my.cnf. Global settings go in /etc/my.cnf. Global to what? All mysql servers running on the machine, or some other definition? I guess my confusion is partially because my.cnf states the port number for both servers and clients, but both servers cant be listening on the same port. Is it the case that i'll need to redefine some of the config options from /etc/my.cnf in DATADIR/my.cnf for each server. If so, thats fine, i just want to make sure i do this correctly, and dont cause an interruption of service in the production server. Most of what i've been reading about running multiple servers on the same box has seemed a bit confusing. thanks much sean peters [EMAIL PROTECTED] On Monday 09 August 2004 12:51, you wrote: Global settings go in /etc/my.cnf. Server-specific settings go in that server's DATADIR/my.cnf. Running multiple servers is documented in the manual http://dev.mysql.com/doc/mysql/en/Multiple_servers.html. Using clients in a multi-server setting is documented on one of the sub-pages. 4.0.13 is over a year old (May 16, 2003). Current version is 4.0.20. A lot has been done in the interim http://dev.mysql.com/doc/mysql/en/News.html. Unless you have a specific reason not to, I'd recommend upgrading to 4.0.20. Michael sean c peters wrote: Hi all, I am looking to upgrade to MySQL 4.0.13 on a Solaris production server, and would like to install and test 4.0.13 without disturbing the existing 4.0.2 server, so that there will be minimal downtime when actually upgrading the production system. So, i should be able to compile 4.0.13 without any problems, by just havnig a different base directory. But, by default, MySQL reads /etc/my.cnf at startup, so im wondering if i'll need to switch out the /etc/my.cnf files depending on which server I'm starting. Also, since client programs get options from that same file, it appears that there will be a problem running them both concurrently, because when a client connects, it will need to read the proper my.cnf, and if i have different clients connecting to each server i'd need to keep switching the files, but i cant realistically know in advance when clients are connecting to which server, so this will not work properly. Can i compile mysql with a different configuration so that it reads the default my.cnf from somewhere else, say /sandbox/etc/my.cnf for instance? Any other problems with running concurrent MySQL servers on the same machine? thanks much sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysqld_multi different server versions
In my ongoing quest to get upgraded to 4.1.3 beta (yes the version I'm upgrading to keeps changing), i have been reading about mysqld_multi to manage multiple server instances on the same machine. But, from what i've read, it appears that this is for running multiple instances of the same server version on one box. Same binary anyway. I say this because all the examples show as varying are the socket, port, pid-file, datadir, language, and user. The [mysqld_multi] directive for my.cnf points mysqld at a particular mysqld_safe, which would imply that all the instances would use the same server. So am i correct in thinking that i wont be able to use mysqld_multi for running two different server versions? This shouldn't be a problem, I dont think i'll need it. Just wanted to check if im missing something. thanks sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Mixing Innodb MyISAM tables
Im considering a design that mixes InnoDB and MyISAM tables. I want Innodb for speed, etc, but i have one table where i want a column to have a FULLTEXT index on. Thus the need for MyISAM. Im not worried about the performance in using the MyISAM tables, as we speak, the production version of the system is using MyISAM tables without problems. The main concern is that by using a MyISAM table, i lose foreign key support, and cannot do a cascade on delete, which i'd really like to have, and not have to manually mimic the cascade behaviour. I suppose i've gotten along fine without having foreign key support for a number of years, so this probably isnt that bad. Anyone else run into similar issues? Any thoughts? thanks much sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB slowness
Hi all, I am in the process of upgrading one of my systems to use InnoDB tables, along with some other tweaks to my code. In any case, i just tried to delete around 7000 records from a table, where there are 9 other tables that will cascade delete when rows from the other table are deleted. Overall, id guess 140,000 rows are being deleted from all tables. This sat for at least 15 minutes, eventually i killed it and it took quite a while for that database to recover. (it was rolling back the tranaction i assume). In any case i didnt expect it to take that long to delete. Im now deleting in chunks of 100 rows in the main table, each chunk is taking 15-30 seconds. This is on a 4 processor sun box running solaris, with 4GB of ram, and a lot of swap (8 GB i think). This is running MySQL 4.0.2 alpha, so that could be part of the issue. Any comments. Should it take this long? thanks sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
load data infile question
I haven't used load data infile much, mainly because of issues like this question. I want to load a bunch of data for our data warehouse into about 10 different tables. But when I load a parent table, an auto_increment column autogenerates a value that will be a foreign key in a child table. So i cant create the file to load into the child table until after the parent table has been loaded. Then i'll need to get back all the auto increment values just created, and put them into the load file for the child tables. Is this how it has to be, or am i missing something? thanks much sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
NULL values
HI all, i am tweaking some tables for an upgrade to MySQL 4.0.13 using InnoDB tables. I have a bunch of columns defaulted to NULL, and have been reading about using NULL's vs defined defaults, such as 0 or ''. I dont really have any need to differentiate between a blank and a null, so i am looking for general performance maintenance concerns. For certain columns i am completely sold on not using nulls, for others, i cant see any conceptual reason to favor either way, so i thought i'd tap you all for some insight. Thanks much. Sean Peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
update statistics question.
IF i run update statistics on MyISAM tables, will those tables lock while the statistics are being updated. This is the first time i think i need to update statistics on a production server, and i dont want to lock out my users for any time. There are about ten tables i'll need to run statistics on, each having between 1.5 million and 25 million rows. Any advice on how to best accomplish this would be great. thanks much, sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
