From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Mike Mascari <mascarm@mascari.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [HACKERS] DISTINCT ON: speak now or forever hold your peace
Date: Mon, 24 Jan 2000 22:09:42 -0500 (EST)
Message-ID: <200001250309.WAA22942@candle.pha.pa.us> (raw)
In-Reply-To: <388D0F84.FF844DF@mascari.com>
> INSERT INTO temp_sales
> SELECT DISTINCT on key supplysources.supplysource,
> incharges.supply, targets.target, incharges.saledate,
> incharges.supplyunit, '', incharges.quantity, incharges.company,
> incharges.costcntr, 'Replenish', incharges.price, '','','', 0,
> text(supplysources.supplysource)||
> text(incharges.supply)||
> text(targets.target)||
> text(incharges.saledate) as key
> FROM supplysources, incharges, targets WHERE
> supplysources.warehouse = incharges.warehouse AND
> (targets.site,targets.area) = (incharges.site,incharges.area);
>
> What happens is that a large charges file which is transferred to
> a mainframe ERP application is first brought into PostgreSQL.
> Depending upon certain race conditions, duplicate "sales" records
> can appear in the data file. We use DISTINCT ON to pick (as you
> point out) an arbitrary record when duplicates appear. I suppose
> we could do a DELETE ... WHERE NOT EXISTS after the import. Using
> DISTINCT ON just saves a step. I don't have any arguments beyond
> the grounds that we're using it in existing code as a duplicate
> record filter - :-(
Why not just throw a NOTICE and keep the feature.
--
Bruce Momjian | http://www.op.net/~candle
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: pgman@candle.pha.pa.us, mascarm@mascari.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] DISTINCT ON: speak now or forever hold your peace
In-Reply-To: <200001250309.WAA22942@candle.pha.pa.us>
References: <388D0F84.FF844DF@mascari.com> <200001250309.WAA22942@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox