4.1.0 subquery problem

------=_NextPart_000_0005_01C34627.DFD39480
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

I have been testing 4.1.0 subqueries and I ran into =
[root@localhost:3306] ERROR 2013: Lost connection to MySQL server during =
query after executing the following:=20

select sum(tbl.sum), sum(cnt) from (select sum, count(*) cnt from wb1 =
group by sum order by cnt desc) tbl

This was done using MySQL Control Center 0.9.2-beta, the latest version =
of Navicat, and the MySQL client for the 4.1.0 version. The error =
message came up after the results were returned correctly to the client.

In the case of MySQL Control Center 0.9.2-beta the message came up =
immediately after the result set was returned. In the latter two cases =
the message did not come up until I tried to execute another select =
statement off of the same database. I was able to reconnect on the =
subsequent execution.

It appears to have something to do with using the group by clause or and =
aggregate function within the derived table. I have had no problems =
doing simple subqueries.

Lee Krawczyk
American Health Group, Inc.
------=_NextPart_000_0005_01C34627.DFD39480--

Re: 4.1.0 subquery problem

Hi!

On Wed, Jul 09, 2003 at 02:39:16PM -0700, Lee Krawczyk wrote:
> Hello,
>
> I have been testing 4.1.0 subqueries and I ran into [root@localhost:3306] ERROR 2013: Lost connection to MySQL server during query after executing the following:
>
> select sum(tbl.sum), sum(cnt) from (select sum, count(*) cnt from wb1 group by sum order by cnt desc) tbl
>
> This was done using MySQL Control Center 0.9.2-beta, the latest version of Navicat, and the MySQL client for the 4.1.0 version. The error message came up after the results were returned correctly to the client.
>
> In the case of MySQL Control Center 0.9.2-beta the message came up immediately after the result set was returned. In the latter two cases the message did not come up until I tried to execute another select statement off of the same database. I was able to reconnect on the subsequent execution.
>
> It appears to have something to do with using the group by clause or and aggregate function within the derived table. I have had no problems doing simple subqueries.

Thank you for information, but above is not enough to repeat this behavour.
Can you provide database schema and some data on which we will able to
repeat this crash. If that data is so big for e-mail then download it,
please, to ftp://support.mysql.com/pub/mysql/secret and inform us.

[skip]

--
For technical support contracts, visit https://order.mysql.com/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Oleksandr Byelkin
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Lugansk, Ukraine
<___/ www.mysql.com

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org