Hi!
Thanks for the bug report. This is now fixed in my local bk tree and the
fix will make its way through the 0.8.7 release.
Regards,
Jorge
--
For technical support contracts, visit https://order.mysql.com/?ref=mjdc
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Jorge del Conde <jorge@stripped>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Mexico City, Mexico
<___/ www.mysql.com
MySQL Users Conference and Expo
http://www.mysql.com/events/uc2003/
----- Original Message -----
From: "Dean Ellis" <dean@stripped>
To: <mysqlcc@stripped>
Sent: Friday, November 22, 2002 1:53 PM
Subject: MySQLCC 0.8.6 and MySQL 4.1
> The EXPLAIN statement in the current BK tree for MySQL 4.1 returns
different
> results than that in earlier versions. Because MySQLCC uses an EXPLAIN
> statement after running queries, and because it determines table names
based
> on the value in the first column of the EXPLAIN result set, it is getting
> confused by the 4.1 result set.
>
> (It is getting an id value from the EXPLAIN instead of the table name, so
it
> then thinks it is working with table `1` instead of table
`table_name_here`.)
>
> Not critical, given that it works fine on the other versions, but I
thought I
> would mention it.
>
> Dean Ellis
>
> ---------------------------------------------------------------------
> Before posting please check: http://www.mysql.com/products/mycc/index.html
> To unsubscribe, send email to
mysqlcc-unsubscribe-jorge=mysql.com@stripped
>
