Re: broken join optimization? (8.0)

From: chester c young <chestercyoung(at)yahoo(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: broken join optimization? (8.0)
Date: 2005-10-26 18:06:32
Message-ID: 20051026180632.62456.qmail@web54301.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> chester c young <chestercyoung(at)yahoo(dot)com> writes:
> > i think i misled: the goal is to retrieve _one_ row where the value
> of each attribute is null.
>
> Er, what for? There's no data content in that, by definition. Why
> not retrieve zero rows and look at the metadata anyway?
>

with a form that is used for CRUD, values are filled in from a record
(either an object or array). when creating, you want an empty record
so that form.item values are set to null. makes for much easier
programming and ensures all variables are defined.

retrieving the metadata and then creating the record seems like a lot
of work when the whole thing can be done with one select (which would
needed in any case to get the metadata).

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Bruno Wolff III 2005-10-26 18:29:10 Re: Combining two SELECTs by same filters
Previous Message Tyler Kellen 2005-10-26 17:48:35 SUM not matching up on a JOIN