Re: broken join optimization? (8.0) - Mailing list pgsql-sql

From chester c young
Subject Re: broken join optimization? (8.0)
Date
Msg-id 20051026180632.62456.qmail@web54301.mail.yahoo.com
Whole thread Raw
In response to Re: broken join optimization? (8.0)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-sql
> Tom Lane <tgl@sss.pgh.pa.us> wrote:

> chester c young <chestercyoung@yahoo.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 


pgsql-sql by date:

Previous
From: Tyler Kellen
Date:
Subject: SUM not matching up on a JOIN
Next
From: Bruno Wolff III
Date:
Subject: Re: Combining two SELECTs by same filters