Re: broken join optimization? (8.0)

Поиск
Список
Период
Сортировка
От chester c young
Тема Re: broken join optimization? (8.0)
Дата
Msg-id 20051026180632.62456.qmail@web54301.mail.yahoo.com
обсуждение исходный текст
Ответ на Re: broken join optimization? (8.0)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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 по дате отправления:

Предыдущее
От: Tyler Kellen
Дата:
Сообщение: SUM not matching up on a JOIN
Следующее
От: Bruno Wolff III
Дата:
Сообщение: Re: Combining two SELECTs by same filters