James Fryer <[EMAIL PROTECTED]> wrote: > I'm using mysql-standard-4.1.0-alpha and I've found a query that > consistently crashes the server. > > The form of the query is this: > >>(SELECT DISTINCT g.id >> FROM T1 b, T2 g >> WHERE g.id IN (0) >> >>) UNION ( >> SELECT DISTINCT b.id >> FROM T1 b, T2 g >> WHERE g.id IN (0) >>) LIMIT 1; > > If I change the IN to '=' or remove the DISTINCTs then it no longer crashes. > > I've run this query on Intel and Power PC architectures and the result is > the same. > > If I run in safe mode, the query no longer causes a crash. Unfortunately > other parts of my application then slow down unacceptably. > > In order to post a bug report I need to winnow down my tables and data to > the minimum, which will take some effort. So before I do this, I'd like to > ask if anyone else has seen this problem and if there is a fix.
Since 4.1.0 many bugs was fixed. Test your query on version 4.1.1 and if you get the same result, provide structure of tables and some data. I tested your query on version 4.1.2 with my test data and all worked like a charm. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [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]
