From: | Jaime Casanova <systemguards(at)yahoo(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Rewritten queries |
Date: | 2004-12-27 19:04:29 |
Message-ID: | 20041227190429.78700.qmail@web50010.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
--- Keith Worthington <keithw(at)narrowpathinc(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-12-27 19:42:25 | Re: Rewritten queries |
Previous Message | Jaime Casanova | 2004-12-27 18:59:29 | Re: Rewritten queries |