Re: Query cache confused when using different client protocols

2005-01-21 Thread Gleb Paharenko
Hello.



Yes. See a long discussion at:

  http://bugs.mysql.com/bug.php?id=6511





Thomas van Gulick [EMAIL PROTECTED] wrote:

 Try this:

 

 Setup a database server, with MySQL 4.1, with query cache turned on

 

 Setup a client machine with MySQL 4.0

 Setup a client machine with MySQL 4.1 (libmysqlclient14)

 

 Create very simple table

 :   CREATE TABLE woepwoep (CNT int NOT NULL);

 

 Insert single row

 :   INSERT INTO woepwoep SET CNT=10;

 

 Now, do select on client machine with MySQL 4.0

 :   SELECT CNT FROM woepwoep;

 

 Query gets cached in format suitable for old protocol

 

 Now, do select on client machine with MySQL 4.1

 :   SELECT CNT FROM woepwoep;

 

 This returns undesirable results. The other way around (initial query done 

 on MySQL 4.1 client, subsequent query done on MySQL 4.0 client) fails too, 

 but then it at least say 'Malformed packet'.

 

 Is this a bug? 

 

 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Query cache confused when using different client protocols

2005-01-20 Thread Thomas van Gulick
Try this:
Setup a database server, with MySQL 4.1, with query cache turned on
Setup a client machine with MySQL 4.0
Setup a client machine with MySQL 4.1 (libmysqlclient14)
Create very simple table
:   CREATE TABLE woepwoep (CNT int NOT NULL);
Insert single row
:   INSERT INTO woepwoep SET CNT=10;
Now, do select on client machine with MySQL 4.0
:   SELECT CNT FROM woepwoep;
Query gets cached in format suitable for old protocol
Now, do select on client machine with MySQL 4.1
:   SELECT CNT FROM woepwoep;
This returns undesirable results. The other way around (initial query done 
on MySQL 4.1 client, subsequent query done on MySQL 4.0 client) fails too, 
but then it at least say 'Malformed packet'.

Is this a bug? 

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]