MySQL Community Server 5.0.85 has been released
Dear MySQL users,
MySQL Community Server 5.0.85, a new version of the popular Open Source
Database Management System, has been released. This and future releases
in the MySQL Community Server 5.0 series share version numbers with
their MySQL Enterprise Server counterparts.
The release is now available in source and binary form for a number of
platforms from our download pages at
http://dev.mysql.com/downloads/
and mirror sites. Note that 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
Due to problems making packages for Linux IA64 compiled with icc
sufficiently
generic, we have decided to not continue providing the IA64, glibc-2.3,
dynamic,
icc tarballs. Note that Red Hat and SuSE specific RPMs for IA64
compiled with
icc are still available.
This section documents all changes and bugfixes that have been
applied since the last MySQL Community Server release (5.0.84).
http://dev.mysql.com/doc/refman/5.0/en/news-5-0-85.html
If you would like to receive more fine-grained and personalized
update alerts about fixes that are relevant to the version and
features you use, please consider subscribing to MySQL Enterprise
(a commercial MySQL offering). For more details please see
http://www.mysql.com/products/enterprise/advisors.html.
Bugs fixed:
* The server printed warnings at startup about adjusting the
value of the max_join_size system variable. (These were
harmless, but might be seen by users as significant.)
(Bug#46385: http://bugs.mysql.com/46385)
* The server crashed if evaluation of GROUP_CONCAT(... ORDER BY)
required allocation of a sort buffer but allocation failed.
(Bug#46080: http://bugs.mysql.com/46080)
* After an error such as a table-full condition, INSERT IGNORE
could cause an assertion failure for debug builds.
(Bug#46075: http://bugs.mysql.com/46075)
* An optimization that moved an item from a subquery to an outer
query could cause a server crash.
(Bug#46051: http://bugs.mysql.com/46051)
* Several Valgrind warnings were corrected.
(Bug#46003: http://bugs.mysql.com/46003,
Bug#46034: http://bugs.mysql.com/46034,
Bug#46042: http://bugs.mysql.com/46042)
* For problems reading SSL files during SSL initialization, the
server wrote error messages to stderr rather than to the error
log. (Bug#45770: http://bugs.mysql.com/45770)
* The vendor name change from MySQL AB to Sun Microsystems, Inc.
in RPM packages was not handled gracefully when upgrading
MySQL using an RPM package.
(Bug#45534: http://bugs.mysql.com/45534)
* Compiler warnings on Windows were fixed.
(Bug#45287: http://bugs.mysql.com/45287)
* Invalid memory reads could occur using the compressed
client/server protocol.
(Bug#45031: http://bugs.mysql.com/45031)
* Invalid input could cause invalid memory reads by the parser.
(Bug#45010: http://bugs.mysql.com/45010)
* The server did not always check the return value of calls to
the hash_init() function.
(Bug#43572: http://bugs.mysql.com/43572)
* A test for stack growth failed on some platforms, leading to
server crashes. (Bug#42213: http://bugs.mysql.com/42213)
* SHOW PROCESSLIST could access freed memory of a stored
procedure run in a concurrent session.
(Bug#38816: http://bugs.mysql.com/38816)
* make_binary_distribution did not always generate correct
distribution names. (Bug#37808: http://bugs.mysql.com/37808)
* The server crashed when executing a prepared statement
containing a duplicated MATCH() function call in the select
list and ORDER BY clause; for example, SELECT MATCH(a)
AGAINST('test') FROM t1 ORDER BY MATCH(a) AGAINST('test').
(Bug#37740: http://bugs.mysql.com/37740)
* If InnoDB reached its limit on the number of concurrent
transactions (1023), it wrote a descriptive message to the
error log but returned a misleading error message to the
client, or an assertion failure occurred.
(Bug#18828: http://bugs.mysql.com/18828)
Thanks
Sunanda
--
Sunanda Menon
Database Technology Group
http://blogs.sun.com/smenon
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Suppressing Warnings
Hi,
I have the following python code:
cursor.execute('create database if not exists spreadsheets;')
cursor.execute('use spreadsheets;')
but it generates this warning:
Warning (from warnings module):
File C:\Python25\mysqlConverter.py, line 140
cursor.execute('use spreadsheets;')
Warning: Can't create database 'spreadsheets'; database exists
What do?
TIA,
Victor
Re: Hi Query Optimization steps
At 05:01 AM 8/22/2009, you wrote: Hi all Tell Me few Query Optimization Tips For example.. some people saying that , avoid using more of and condition in the query Huh? You need to carefully plan your table structure and use indexes sparingly on the columns you are using in the Where clauses. An EXPLAIN in front of the Select statement will show you which indexes it is using. This sort of very basic things please tell me ... Also tell me , in the optimization view ,, which database engine is best If you need transactions or RI then you have to use InnoDb. Otherwise MyISAM is quite fast. Again it depends on the type of queries you are executing. Thanks Bharanikumar There is no magic wand to getting MySQL to run faster except planning and knowledge. It will take some effort on your part but it will be fun. Take a look at High Performance MySQL 2nd Edition. Some of the first edition is online at http://books.google.com/books?id=sgMvu2uZXlsCprintsec=frontcoverdq=high+performance+mysql#v=onepageq=f=false You can get the second edition at Amazon. Also you may need to read other MySQL books like MySQL Cookbook http://books.google.com/books?id=aC3blgT3D3YCprintsec=frontcoverdq=mysql+cookbook#v=onepageq=f=false The 2nd edition is at Amazon. or MySQL by Paul DuBois is also quite good. These will get you started on the right foot. Mike -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: Scaling Mysql
Have you looked at MySQL cluster? It was created specifically for telco needs. -Original Message- From: Krishna Chandra Prajapati [mailto:prajapat...@gmail.com] Sent: Friday, August 21, 2009 9:23 PM To: wha...@bfs.de Cc: MySQL Subject: Re: Scaling Mysql Hi wharms, Yor are right. It's some kind of queue mechanism. Right now i am working i telco company (We used to send sms) Users will be inserting records into send_sms @ 30,000msg/min Then those record will be updated and moved to alt_send_sms and deleted from send_sms. After that 30,000msg/min will be taken out from alt_send for processing and sending to client. All the above task are happening concurrently. We will be dealing with million of records/hour On Fri, Aug 21, 2009 at 6:11 PM, walter harms wha...@bfs.de wrote: Krishna Chandra Prajapati schrieb: Hi list, I have two tables send_sms and alt_send_sms. Users are inserting records into send_sms @ 500/sec ie 3/min. After applying some updates to send_sms data are transferred to alt_send_sms and deleted from send sms. The same thing is happening with alt_send_sms table. Is it possible to insert 1000records/sec in send_sms table and taken out at the rate 1000records/seconds from alt_send_sms. Which engine is more better for the above senario. Hi Krishna, i see you are using some kind of queue mechanism but to get a useful answer you need to be more specific: e.g. what are your safety requirements ? After moving the data to next stage Data is deleted from current table. Tables in RAM are very fast. e.g. do you need forgein keys ? No When will data be copied (send-alt) ? 3records/min after 1 day ? 1 hour ? how long to you need to store data at alt ? Min 1 minute (we need to process immeaditely and send to the users as sms) how often is the access ? per/sec If speed is a concern do you need a database at all ? (KISS) where does the current system spend its time ? and why ? You see your request is far from simple and demands detail knowlegde about your requirements going beyound what can be done in such a ML (and this is only software, there is also hardware an economics). Here you can ask how can i improve SQL statement XX ? re, wh Thanks krishna The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL Encryption - Third-party tools
Hello, all. Can any of you share with me the names of any third-party tools or appliances that you are using to encrypt your MySQL databases? I am doing a search and would like to narrow down the initial search list. Thanks! Mike
Natural Join Issue: column names are equal but doesn't work anyways
Hello,
I have been training for a test on Database Design and MySQL.
The following is inside a file we have to run before starting to code
what the excercises require us to.
Call the file as you wish and run it if it helps to understand the
reason behind my problem.
---
DROP DATABASE IF EXISTS premiere;
CREATE DATABASE premiere;
USE premiere;
create table if not exists Articoli(
NroArt char(4) primary key,
descrizione char(20),
giacenza int,
categoria char (2),
PrezzoUnitario decimal(8,2)
) TYPE=INNODB;
create table if not exists Rappresentanti(
CodRappr char(2) primary key,
cognome char(10),
nome char(8),
via char (15),
citta char(15),
prov char(2),
cap char (5),
TotProvv decimal(8,2),
PerProvv decimal(8,2)
) TYPE=INNODB;
create table if not exists clienti(
CodCliente char(3) primary key,
cognome char(10),
nome char(8),
via char (15),
citta char(15),
prov char(2),
cap char (5),
saldo decimal(8,2),
fido decimal(8,2),
CodRappr char(2) not null references
Rappresentanti(CodRappr)
) TYPE=INNODB;
create table if not exists Ordini(NroOrdine char(6) primary key,
data date,
CodCliente char(3) not null
references Clienti(CodClienti)
) TYPE=INNODB;
insert into articoli
values ('AX12','ferro da stiro',104,'cs',24.95);
insert into articoli
values ('AZ52','freccette',20,'sp',12.95);
insert into articoli
values ('BA74','pallone',40,'sp',29.95);
insert into articoli
values ('BH22','tritatutto',05,'cs',24.95);
insert into articoli
values ('BT04','forno',11,'el',149.49);
insert into articoli
values ('BZ66','lavatrice',52,'el',399.99);
insert into articoli
values ('CA14','setaccio',78,'cs',39.99);
insert into articoli
values ('CB03','bicicletta',44,'sp',299.99);
insert into articoli
values ('CX11','frullino',142,'cs',22.95);
insert into articoli
values ('CZ81','tavola pesi',68,'sp',349.95);
insert into Rappresentanti
values('03','Jones','Mary','123 Main','Grant','MI','49219',215,5);
insert into Rappresentanti
values('06','Smith','William','102
Raymond','Ada','MI','49441',49412.5,7);
insert into Rappresentanti
values('12','Diaz','Miguel','419 Harper','Lansing','MI','49224',2150,5);
insert into clienti
values
('124','Adams','Sally','481Oak','Lansing','MI','49224',818.75,1000,'03');
insert into clienti
values
('256','Samuel','Ann','215Pete','Grant','MI','49219',21.5,1500,'06');
insert into clienti
values
('311','Charles','Don','48College','Ira','MI','49034',825.75,1000,'12');
insert into clienti
values
('315','Daniels','Tom','914Charry','Kent','MI','48391',770.75,750,'06');
insert into clienti
values
('405','Williams','Al','519Watson','Grant','MI','49219',402.75,1500,'12');
insert into clienti
values
('412','Adams','Sally','16Elm','Lansing','MI','49224',1817.5,2000,'03');
insert into clienti
values
('522','Nelson','Mary','108Pine','Ada','MI','49441',98.75,1500,'12');
insert into clienti
values
('567','Dinh','Tran','808Ridge','Harper','MI','48421',402.4,750,'06');
insert into clienti
values
('587','Galvez','Mara','512Pine','Ada','MI','49441',114.6,1000,'06');
insert into clienti
values
('622','Martin','Dan','419Chip','Grant','MI','49219',1045.75,1000,'03');
insert into ordini
values('12489','2002-09-02','124');
insert into ordini
values('12491','2002-09-02','311');
insert into ordini
values('12494','2002-09-04','315');
insert into ordini
values('12495','2002-09-04','256');
insert into ordini
values('12498','2002-09-05','522');
insert into ordini
values('12500','2002-09-05','124');
insert into ordini
values('12504','2002-09-05','522');
-
Now, this is what is giving me an issue:
---
use premiere;
select *
from clienti as c join rappresentanti as r on c.codrappr = r.codrappr
where r.codrappr='03';
select *
from rappresentanti NATURAL JOIN clienti;
--
For some weird reason the natural join returns an empty set, but there
is a column, just the one I need whose name is the same
in both relations which is Codrappr.
Why doesn't it work as it's supposed to?
As you can see they are the same:
create table if not exists Rappresentanti(
CodRappr char(2) primary key,
cognome char(10),
nome char(8),
via char (15),
Re: Natural Join Issue: column names are equal but doesn't work anyways
Hi again,
since I'm not someone who gives up easily, I have restyled that old code
(actually is from an example back of my teacher into 2002, I saw that
she changed a bit her way to code this stuff), I restyled the code just
to be sure it isn't some parsing issue or whatever.
http://pastebin.com/f50d77dcf
On that database, this query works:
select CodCliente, Cognome, Nome from Ordini NATURAL JOIN Clienti where
Data='2002-09-05';
whereas this one does not:
select *
from rappresentanti NATURAL JOIN clienti;
I pasted the database in there.
Deviad ha scritto:
Hello,
I have been training for a test on Database Design and MySQL.
The following is inside a file we have to run before starting to code
what the excercises require us to.
Call the file as you wish and run it if it helps to understand the
reason behind my problem.
---
DROP DATABASE IF EXISTS premiere;
CREATE DATABASE premiere;
USE premiere;
create table if not exists Articoli(
NroArt char(4) primary key,
descrizione char(20),
giacenza int,
categoria char (2),
PrezzoUnitario decimal(8,2)
) TYPE=INNODB;
create table if not exists Rappresentanti(
CodRappr char(2) primary key,
cognome char(10),
nome char(8),
via char (15),
citta char(15),
prov char(2),
cap char (5),
TotProvv decimal(8,2),
PerProvv decimal(8,2)
) TYPE=INNODB;
create table if not exists clienti(
CodCliente char(3) primary key,
cognome char(10),
nome char(8),
via char (15),
citta char(15),
prov char(2),
cap char (5),
saldo decimal(8,2),
fido decimal(8,2),
CodRappr char(2) not null references
Rappresentanti(CodRappr)
) TYPE=INNODB;
create table if not exists Ordini(NroOrdine char(6) primary key,
data date,
CodCliente char(3) not null
references Clienti(CodClienti)
) TYPE=INNODB;
insert into articoli
values ('AX12','ferro da stiro',104,'cs',24.95);
insert into articoli
values ('AZ52','freccette',20,'sp',12.95);
insert into articoli
values ('BA74','pallone',40,'sp',29.95);
insert into articoli
values ('BH22','tritatutto',05,'cs',24.95);
insert into articoli
values ('BT04','forno',11,'el',149.49);
insert into articoli
values ('BZ66','lavatrice',52,'el',399.99);
insert into articoli
values ('CA14','setaccio',78,'cs',39.99);
insert into articoli
values ('CB03','bicicletta',44,'sp',299.99);
insert into articoli
values ('CX11','frullino',142,'cs',22.95);
insert into articoli
values ('CZ81','tavola pesi',68,'sp',349.95);
insert into Rappresentanti
values('03','Jones','Mary','123 Main','Grant','MI','49219',215,5);
insert into Rappresentanti
values('06','Smith','William','102
Raymond','Ada','MI','49441',49412.5,7);
insert into Rappresentanti
values('12','Diaz','Miguel','419 Harper','Lansing','MI','49224',2150,5);
insert into clienti
values
('124','Adams','Sally','481Oak','Lansing','MI','49224',818.75,1000,'03');
insert into clienti
values
('256','Samuel','Ann','215Pete','Grant','MI','49219',21.5,1500,'06');
insert into clienti
values
('311','Charles','Don','48College','Ira','MI','49034',825.75,1000,'12');
insert into clienti
values
('315','Daniels','Tom','914Charry','Kent','MI','48391',770.75,750,'06');
insert into clienti
values
('405','Williams','Al','519Watson','Grant','MI','49219',402.75,1500,'12');
insert into clienti
values
('412','Adams','Sally','16Elm','Lansing','MI','49224',1817.5,2000,'03');
insert into clienti
values
('522','Nelson','Mary','108Pine','Ada','MI','49441',98.75,1500,'12');
insert into clienti
values
('567','Dinh','Tran','808Ridge','Harper','MI','48421',402.4,750,'06');
insert into clienti
values
('587','Galvez','Mara','512Pine','Ada','MI','49441',114.6,1000,'06');
insert into clienti
values
('622','Martin','Dan','419Chip','Grant','MI','49219',1045.75,1000,'03');
insert into ordini
values('12489','2002-09-02','124');
insert into ordini
values('12491','2002-09-02','311');
insert into ordini
values('12494','2002-09-04','315');
insert into ordini
values('12495','2002-09-04','256');
insert into ordini
values('12498','2002-09-05','522');
insert into ordini
values('12500','2002-09-05','124');
insert into ordini
values('12504','2002-09-05','522');
-
Now, this is what is giving me an issue:
Re: Natural Join Issue: column names are equal but doesn't work anyways
On Tue, Aug 25, 2009 at 6:55 AM, Deviad dev...@msn.com wrote:
Hello,
I have been training for a test on Database Design and MySQL.
The following is inside a file we have to run before starting to code
what the excercises require us to.
Call the file as you wish and run it if it helps to understand the
reason behind my problem.
---
DROP DATABASE IF EXISTS premiere;
CREATE DATABASE premiere;
USE premiere;
create table if not exists Articoli(
NroArt char(4) primary key,
descrizione char(20),
giacenza int,
categoria char (2),
PrezzoUnitario decimal(8,2)
) TYPE=INNODB;
create table if not exists Rappresentanti(
CodRappr char(2) primary key,
cognome char(10),
nome char(8),
via char (15),
citta char(15),
prov char(2),
cap char (5),
TotProvv decimal(8,2),
PerProvv decimal(8,2)
) TYPE=INNODB;
create table if not exists clienti(
CodCliente char(3) primary key,
cognome char(10),
nome char(8),
via char (15),
citta char(15),
prov char(2),
cap char (5),
saldo decimal(8,2),
fido decimal(8,2),
CodRappr char(2) not null references
Rappresentanti(CodRappr)
) TYPE=INNODB;
create table if not exists Ordini(NroOrdine char(6) primary key,
data date,
CodCliente char(3) not null
references Clienti(CodClienti)
) TYPE=INNODB;
insert into articoli
values ('AX12','ferro da stiro',104,'cs',24.95);
insert into articoli
values ('AZ52','freccette',20,'sp',12.95);
insert into articoli
values ('BA74','pallone',40,'sp',29.95);
insert into articoli
values ('BH22','tritatutto',05,'cs',24.95);
insert into articoli
values ('BT04','forno',11,'el',149.49);
insert into articoli
values ('BZ66','lavatrice',52,'el',399.99);
insert into articoli
values ('CA14','setaccio',78,'cs',39.99);
insert into articoli
values ('CB03','bicicletta',44,'sp',299.99);
insert into articoli
values ('CX11','frullino',142,'cs',22.95);
insert into articoli
values ('CZ81','tavola pesi',68,'sp',349.95);
insert into Rappresentanti
values('03','Jones','Mary','123 Main','Grant','MI','49219',215,5);
insert into Rappresentanti
values('06','Smith','William','102
Raymond','Ada','MI','49441',49412.5,7);
insert into Rappresentanti
values('12','Diaz','Miguel','419 Harper','Lansing','MI','49224',2150,5);
insert into clienti
values
('124','Adams','Sally','481Oak','Lansing','MI','49224',818.75,1000,'03');
insert into clienti
values
('256','Samuel','Ann','215Pete','Grant','MI','49219',21.5,1500,'06');
insert into clienti
values
('311','Charles','Don','48College','Ira','MI','49034',825.75,1000,'12');
insert into clienti
values
('315','Daniels','Tom','914Charry','Kent','MI','48391',770.75,750,'06');
insert into clienti
values
('405','Williams','Al','519Watson','Grant','MI','49219',402.75,1500,'12');
insert into clienti
values
('412','Adams','Sally','16Elm','Lansing','MI','49224',1817.5,2000,'03');
insert into clienti
values
('522','Nelson','Mary','108Pine','Ada','MI','49441',98.75,1500,'12');
insert into clienti
values
('567','Dinh','Tran','808Ridge','Harper','MI','48421',402.4,750,'06');
insert into clienti
values
('587','Galvez','Mara','512Pine','Ada','MI','49441',114.6,1000,'06');
insert into clienti
values
('622','Martin','Dan','419Chip','Grant','MI','49219',1045.75,1000,'03');
insert into ordini
values('12489','2002-09-02','124');
insert into ordini
values('12491','2002-09-02','311');
insert into ordini
values('12494','2002-09-04','315');
insert into ordini
values('12495','2002-09-04','256');
insert into ordini
values('12498','2002-09-05','522');
insert into ordini
values('12500','2002-09-05','124');
insert into ordini
values('12504','2002-09-05','522');
-
Now, this is what is giving me an issue:
---
use premiere;
select *
from clienti as c join rappresentanti as r on c.codrappr = r.codrappr
where r.codrappr='03';
select *
from rappresentanti NATURAL JOIN clienti;
--
For some weird reason the natural join returns an empty set, but there
is a column, just the one I need whose name is the same
in both relations which is Codrappr.
Why doesn't it work as it's supposed to?
As you can see they are the same:
create table if not exists Rappresentanti(
Re: Suppressing Warnings
Warning: Can't create database 'spreadsheets'; database exists
This is the answer.
2009/8/24 Victor Subervi victorsube...@gmail.com
Hi,
I have the following python code:
cursor.execute('create database if not exists spreadsheets;')
cursor.execute('use spreadsheets;')
but it generates this warning:
Warning (from warnings module):
File C:\Python25\mysqlConverter.py, line 140
cursor.execute('use spreadsheets;')
Warning: Can't create database 'spreadsheets'; database exists
What do?
TIA,
Victor
Re: Scaling Mysql
Yes, it's in our planning On Mon, Aug 24, 2009 at 11:10 PM, Gavin Towey gto...@ffn.com wrote: Have you looked at MySQL cluster? It was created specifically for telco needs. -Original Message- From: Krishna Chandra Prajapati [mailto:prajapat...@gmail.com] Sent: Friday, August 21, 2009 9:23 PM To: wha...@bfs.de Cc: MySQL Subject: Re: Scaling Mysql Hi wharms, Yor are right. It's some kind of queue mechanism. Right now i am working i telco company (We used to send sms) Users will be inserting records into send_sms @ 30,000msg/min Then those record will be updated and moved to alt_send_sms and deleted from send_sms. After that 30,000msg/min will be taken out from alt_send for processing and sending to client. All the above task are happening concurrently. We will be dealing with million of records/hour On Fri, Aug 21, 2009 at 6:11 PM, walter harms wha...@bfs.de wrote: Krishna Chandra Prajapati schrieb: Hi list, I have two tables send_sms and alt_send_sms. Users are inserting records into send_sms @ 500/sec ie 3/min. After applying some updates to send_sms data are transferred to alt_send_sms and deleted from send sms. The same thing is happening with alt_send_sms table. Is it possible to insert 1000records/sec in send_sms table and taken out at the rate 1000records/seconds from alt_send_sms. Which engine is more better for the above senario. Hi Krishna, i see you are using some kind of queue mechanism but to get a useful answer you need to be more specific: e.g. what are your safety requirements ? After moving the data to next stage Data is deleted from current table. Tables in RAM are very fast. e.g. do you need forgein keys ? No When will data be copied (send-alt) ? 3records/min after 1 day ? 1 hour ? how long to you need to store data at alt ? Min 1 minute (we need to process immeaditely and send to the users as sms) how often is the access ? per/sec If speed is a concern do you need a database at all ? (KISS) where does the current system spend its time ? and why ? You see your request is far from simple and demands detail knowlegde about your requirements going beyound what can be done in such a ML (and this is only software, there is also hardware an economics). Here you can ask how can i improve SQL statement XX ? re, wh Thanks krishna The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
