Hello,
I must be missing something. When Manager creates a JOIN, it adds a OR
(tN.FK IS NULL) to the where clause even though FK is defined as
not_null = 1 in tN. Adding this clause really extends the query time on
some queries. I just tested one with and without the OR clause; with
took 9
On 12/5/06 9:50 AM, Kurt Hansen wrote:
I must be missing something. When Manager creates a JOIN, it adds a OR
(tN.FK IS NULL) to the where clause even though FK is defined as
not_null = 1 in tN. [...]
Here are the offending FROM and WHERE clauses:
FROM
transactions t1
LEFT OUTER
Hi Kurt
could be added to the documentation of Manager or QueryBuilder or to an
FAQ, e.g. What to look for if your MySQL query is afully slow. :-)
Another database vendor?
(I tried to resist, truely).
--
Ron Savage
[EMAIL PROTECTED]
http://savage.net.au/index.html
