Re: Rewritten queries - Mailing list pgsql-novice

From Jaime Casanova
Subject Re: Rewritten queries
Date
Msg-id 20041227190429.78700.qmail@web50010.mail.yahoo.com
Whole thread Raw
In response to Rewritten queries  ("Keith Worthington" <keithw@narrowpathinc.com>)
Responses Re: Rewritten queries
List pgsql-novice
 --- Keith Worthington <keithw@narrowpathinc.com>
escribió:
> Hi All,
>
> I wrote a query that created a view and when I
> looked at it in the database
> the SELECT statement was very different.  In part
>
> SELECT items.id,
>        COALESCE(sales.sum, 0) AS committed,
>        COALESCE(purchases.sum, 0) AS on_order,
>        COALESCE(stock.quantity, 0) AS on_hand
>   FROM peachtree.tbl_item AS items...
>
> was changed to
>
> CREATE OR REPLACE VIEW interface.view_inventory AS
>
>  SELECT items.id,
>         CASE
>             WHEN (sales.sum IS NOT NULL ) THEN
> sales.sum
>             WHEN (0 IS NOT NULL ) THEN (0 )::real
>             ELSE NULL::real
>         END  AS "committed",
>         CASE
>             WHEN (purchases.sum IS NOT NULL ) THEN
> purchases.sum
>             WHEN (0 IS NOT NULL ) THEN (0 )::real
>             ELSE NULL::real
>         END  AS on_order,
>         CASE
>             WHEN (stock.quantity IS NOT NULL ) THEN
> stock.quantity
>             WHEN (0 IS NOT NULL ) THEN (0 )::real
>             ELSE NULL::real
>         END  AS on_hand
>    FROM (((peachtree.tbl_item items
>
What version of postgres are u using?
I don't see that particular behavior in coalesce.

someone knows if this is the behavior in any older
version of pg?

regards,
Jaime Casanova

_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com

pgsql-novice by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: Rewritten queries
Next
From: Tom Lane
Date:
Subject: Re: Rewritten queries