Re: Query issue/8.0.1/Serendipity

From: Larry Rosenman <ler(at)lerctr(dot)org>
To: Michael Glaesemann <grzm(at)myrealbox(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Query issue/8.0.1/Serendipity
Date: 2005-03-08 12:28:38
Message-ID: 200503080628.39117.ler@lerctr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Tuesday 08 March 2005 06:21 am, Michael Glaesemann wrote:
> Larry,
>
> Restating your SQL in a more reader-friendly form:
[snip]
>
This is from an error page (and machine generated to boot :) )

> I can see you're using a lot of left joins. You are beginning your left
> joins off of ec, so I believe neither e nor c can be referenced as join
> conditions. It might work if you reorder the first part of the FROM
> clause as the following:
>
> FROM serendipity_category c
> , serendipity_entrycat ec
> , serendipity_entries e
> LEFT OUTER JOIN serendipity_entryproperties ep_cache_extended
>
> (Thugh I can't be sure without seeing table definitions.)
a pg_dump -s is at:

http://www.lerctr.org/~ler/s9y.sql

>
> It also appears you have a redundant e.timestamp constraint in the
> WHERE clause: if e.timestamp is >= 1110241185 it's definitely going to
> be <= 1112335200
this query is machine generated, so I'm sure it's based on timestamps.

>
> Hope this helps. I find white space helps me read my own SQL much more
> easily.

understood, as I said, it's machine generated :)

>
> Michael Glaesemann
> grzm myrealbox com

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-351-4152 E-Mail: ler(at)lerctr(dot)org
US Mail: 3535 Gaspar Drive, Dallas, TX 75220-3611

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Larry Rosenman 2005-03-08 12:29:48 Re: Query issue/8.0.1/Serendipity
Previous Message Michael Glaesemann 2005-03-08 12:21:08 Re: Query issue/8.0.1/Serendipity