Re: [mysql 4.0.14-nt] MySQL eats my CPU with speical SELECT statement
Frank Schönheit <[email protected]>
| Newsgroups | gmane.comp.db.mysql.bugs |
|---|---|
| Organization | StarOffice Software Entwicklungs GmbH; Sun Microsystems, Inc. |
| Message-ID | <[email protected]> |
Hi Alexander, >> What I wanted (means: failed :) to express was that I associated the "0 >> = 1" I saw with the "WHERE 0 = 1" which OOo regularily uses to determine >> the structure of a result set. > > Really? > I would never expect this! > With MySQL there is much nicer way to check if query syntax is Ok and it > works with all queries and all possible WHERE, GROUP BY and HAVING clauses. > > ... LIMIT 0; The problem is that OpenOffice.org does not rely on a fixed backend - it should work with a lot more backends than MySQL - at least until MySQL (or any other database, for that matter :) reaches world domination and there will be no other databases anymore ... "WHERE 0 = 1" is the least common denominator, it's expected that most halfway modern databases have an optimization for it. >> Hmm. You mean I have migrate to Linux? :) Okay, that's becoming >> off-topic ... :) > > No! I mean that I gave it a try and there were nothing wrong with CPU > usage. just kidding ... Thanks & Ciao Frank -- MySQL Bugs Mailing List For list archives: http://lists.mysql.com/bugs To unsubscribe: http://lists.mysql.com/[email protected]