Clusterring, Fail over (High Availability) and Load Balancing With Ubuntu 8.04
Is it possible to do load balancing with 3 servers which also cluster and fail over (High Availibity) with MySQL? Can somebody give me the how to or URL to setup? Willy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL Community Server 5.1.35 has been released
Dear MySQL users, MySQL Community Server 5.1.35, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.35 is recommended for use on production systems. For an overview of what's new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html For information on installing MySQL 5.1.35 on new servers or upgrading to MySQL 5.1.35 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://forge.mysql.com/wiki/Contributing For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-35.html Enjoy! Timothy Smith The MySQL build team at Sun Microsystems === This release of MySQL has two known outstanding issues for Windows: * The .msi installer does not detect an existing root password on the initial configuration attempt. To work around this, install and configure MySQL as normal, but skip any changes to security. (There is a checkbox that allows this on the security screen of the configuration wizard.) Then check your settings: + If the old root password and security settings are okay, you are done and can proceed to use MySQL. + Otherwise, reconfigure with the wizard and make any changes on the second configuration attempt. The wizard will properly prompt for the existing root password and allow changes to be made. This issue has been filed as Bug#45200: http://bugs.mysql.com/45200 for correction in a future release. * The Windows configuration wizard allows changes to InnoDB settings during a reconfiguration operation. For an upgrade, this may cause difficulties. To work around this, use one of the following alternatives: + Do not change InnoDB settings. + Copy files from the old InnoDB location to the new one. This issue has been filed as Bug#45201: http://bugs.mysql.com/45201 for correction in a future release. Bugs fixed: * Important Change: Replication: The transactional behavior of STOP SLAVE has changed. Formerly, it took effect immediately, even inside a transaction; now, it waits until the current replication event group (if any) has finished executing, or until the user issues a KILL QUERY or KILL CONNECTION statement. This was done in order to solve the problem encountered when replication was stopped while a nontransactional slave was replicating a transaction on the master. (It was impossible to roll back a mixed-engines transaction when one of the engines was nontransactional, which meant that the slave could not safely re-apply any transaction that had been interrupted by STOP SLAVE.) (Bug#319: http://bugs.mysql.com/319, Bug#38205: http://bugs.mysql.com/38205) See also Bug#43217: http://bugs.mysql.com/43217. * Partitioning: When a value was equal to a PARTITION ... VALUES LESS THAN (value) value other than MAXVALUE, the corresponding partition was not pruned. (Bug#42944: http://bugs.mysql.com/42944) * Replication: Unrelated errors occurring during the execution of RESET SLAVE could cause the slave to crash. (Bug#44179: http://bugs.mysql.com/44179) * Replication: The --slave-skip-errors option had no effect when using row-based logging format. (Bug#39393: http://bugs.mysql.com/39393) * Replication: The following erors were not correctly reported: + Failures during slave thread initialization + Failures while initializing the relay log position (immediately following the starting of the slave thread) + Failures while processing queries passed through the --init_slave option. Information about these types of failures can now be found in the output of SHOW SLAVE STATUS. (Bug#38197: http://bugs.mysql.com/38197) * Replication: Killing the thread executing a DDL statement, after it had finished its execution but before it had written the binlog event, caused the error code in the binlog event to be set (incorrectly) to ER_SERVER_SHUTDOWN or ER_QUERY_INTERRUPTED, which caused replication to fail. (Bug#37145: http://bugs.mysql.com/37145) See also
Re: How to check whether the lock is a share lock or exclusive lock?
Ok. I have already gotten the answer. On Wed, Jun 3, 2009 at 4:15 PM, Moon's Father yueliangdao0...@gmail.comwrote: Hi. I want to know which lock method is used within MySQL? For example, if I query the following statements within MySQL client. mysql begin; Query OK, 0 rows affected (0.00 sec) mysql select * from GroupId_Test where id = 212 lock in share mode; +-+-+ | id | GroupId | +-+-+ | 212 | 3014485 | +-+-+ 1 row in set (0.00 sec) But when I execute statement called show engine innodb status, it only display the total lock numbers. Anybody can tell me how to see whether the lock is a share lock or exclusive lock? -- David Yeung, MySQL Senior Support Engineer, Sun Gold Partner. My Blog:http://yueliangdao0608.cublog.cn -- David Yeung, MySQL Senior Support Engineer, Sun Gold Partner. My Blog:http://yueliangdao0608.cublog.cn
Does MySQL have the same function as the ORACLE TDE technique?
Hi. Here is the introduction. http://www.oracle.com/technology/oramag/oracle/05-sep/o55security.html I want to know whether MySQL has the same function as Oracle's? Any reply is appreciated. -- David Yeung, MySQL Senior Support Engineer, Sun Gold Partner. My Blog:http://yueliangdao0608.cublog.cn
Re: How to check whether the lock is a share lock or exclusive lock?
Mind sharing ? :-) I don't really have the issue, but it sounds like a useful trick. On Fri, Jun 5, 2009 at 11:44 AM, Moon's Father yueliangdao0...@gmail.comwrote: Ok. I have already gotten the answer. On Wed, Jun 3, 2009 at 4:15 PM, Moon's Father yueliangdao0...@gmail.com wrote: Hi. I want to know which lock method is used within MySQL? For example, if I query the following statements within MySQL client. mysql begin; Query OK, 0 rows affected (0.00 sec) mysql select * from GroupId_Test where id = 212 lock in share mode; +-+-+ | id | GroupId | +-+-+ | 212 | 3014485 | +-+-+ 1 row in set (0.00 sec) But when I execute statement called show engine innodb status, it only display the total lock numbers. Anybody can tell me how to see whether the lock is a share lock or exclusive lock? -- David Yeung, MySQL Senior Support Engineer, Sun Gold Partner. My Blog:http://yueliangdao0608.cublog.cn -- David Yeung, MySQL Senior Support Engineer, Sun Gold Partner. My Blog:http://yueliangdao0608.cublog.cn -- Celsius is based on water temperature. Fahrenheit is based on alcohol temperature. Ergo, Fahrenheit is better than Celsius. QED.
Trigger and Warning: #1265 Data truncated
I'm very new to triggers, so I suspect I've done something naive. When a row is inserted into a table, I want populate a 'date' column with the date 45 days hence. I've created a trigger: CREATE TRIGGER `test`.`setExpiryDate` BEFORE INSERT ON `test`.`mysql_auth` FOR EACH ROW SET NEW.expires = curdate()+interval 45 day It works, doing what I want, but I get the following error: Warning: #1265 Data truncated for column 'expires' at row 1 The table is: CREATE TABLE `mysql_auth` ( `id` int(11) NOT NULL auto_increment, `user` varchar(25) NOT NULL, `password` varchar(32) NOT NULL, `expires` date NOT NULL, `login_failures` int(11) NOT NULL default '0', `last_login_failure` datetime default NULL, PRIMARY KEY (`id`) ) Can someone help me understand what it happening here, and how to fix it? Thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Trigger and Warning: #1265 Data truncated
Curdate() returns a datetime, which you are pushing into a date field. It is truncating the time part. Just truncate it and you should be fine :) Walter On Fri, Jun 5, 2009 at 5:56 AM, Keith Edmundsk...@midnighthax.com wrote: I'm very new to triggers, so I suspect I've done something naive. When a row is inserted into a table, I want populate a 'date' column with the date 45 days hence. I've created a trigger: CREATE TRIGGER `test`.`setExpiryDate` BEFORE INSERT ON `test`.`mysql_auth` FOR EACH ROW SET NEW.expires = curdate()+interval 45 day It works, doing what I want, but I get the following error: Warning: #1265 Data truncated for column 'expires' at row 1 The table is: CREATE TABLE `mysql_auth` ( `id` int(11) NOT NULL auto_increment, `user` varchar(25) NOT NULL, `password` varchar(32) NOT NULL, `expires` date NOT NULL, `login_failures` int(11) NOT NULL default '0', `last_login_failure` datetime default NULL, PRIMARY KEY (`id`) ) Can someone help me understand what it happening here, and how to fix it? Thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=li...@olindata.com -- Walter Heck, Engineer @ Open Query (http://openquery.com) Affordable Training and ProActive Support for MySQL related technologies Follow our blog at http://openquery.com/blog/ OurDelta: free enhanced builds for MySQL @ http://ourdelta.org -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Ordering an IN query
I have a query that I build dynamically, here is an example:
select from (table1 as t1 left join table2 as t2 on t1.id = t2.id)
left join table3 as t3 on t1.id = t3.id where t1.id in ('221593',
'221591', 'CC3762', 'CC0059')
So I build the query in the order that I want it displayed. That is
display 221593, then 221591, then CC3762, etc. However, when the
query is executed it looks like it automatically sorts the codes in
ascending order, so I get 221591, then 221593, the CC0059, etc.
I want the results displayed in the order that I build the query. Is
there some way of doing that?
Thanks,
-Aaron
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: Ordering an IN query
Aaron-
to reorder results of a column specify
FIELD(ColumnName,1stPosition,2ndPosition) e.g.
mysqluse information_schema;
mysql select ordinal_position,TABLE_CATALOG,TABLE_SCHEMA,TABLE_NAME,COLUMN_NAME
from COLUMNS WHERE ORDINAL_POSITION=23 OR ORDINAL_POSITION=18 ORDER BY
FIELD(ORDINAL_POSITION,23,18);
Shalom
Martin Gainty
__
Note de déni et de confidentialité
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
From: afisc...@smith.edu
To: mysql@lists.mysql.com
Subject: Ordering an IN query
Date: Fri, 5 Jun 2009 09:09:24 -0400
I have a query that I build dynamically, here is an example:
select from (table1 as t1 left join table2 as t2 on t1.id = t2.id)
left join table3 as t3 on t1.id = t3.id where t1.id in ('221593',
'221591', 'CC3762', 'CC0059')
So I build the query in the order that I want it displayed. That is
display 221593, then 221591, then CC3762, etc. However, when the
query is executed it looks like it automatically sorts the codes in
ascending order, so I get 221591, then 221593, the CC0059, etc.
I want the results displayed in the order that I build the query. Is
there some way of doing that?
Thanks,
-Aaron
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=mgai...@hotmail.com
_
Hotmail® has ever-growing storage! Don’t worry about storage limits.
http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage_062009
Re: Ordering an IN query
On Fri, Jun 5, 2009 at 9:09 AM, Aaron Fischerafisc...@smith.edu wrote: So I build the query in the order that I want it displayed. That is display 221593, then 221591, then CC3762, etc. However, when the query is executed it looks like it automatically sorts the codes in ascending order, so I get 221591, then 221593, the CC0059, etc. I want the results displayed in the order that I build the query. Is there some way of doing that? You'll have to use a function like CASE() or FIND_IN_SET() to map the IDs to values in an ORDER BY clause. - Perrin -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
