On Tue, Jan 28, 2003 at 20:05:15 +1300,
Rodger Donaldson <[EMAIL PROTECTED]> wrote:
>
> The problem: I have two tables, add_queue and sites, on a postgresql
> 7.2.x database. add_queue is where items go to be reviewed by a human
> before being moved into sites. One of the things I'd like to do
> On Tue, 28 Jan 2003, Rodger Donaldson wrote:
>
> > Now, adding a UNIQUE constraint on the pk for add_queue weeds out
> > dupes there. However, attempting to add a cross-table UNIQUE check
> > with:
> >
> > alter table add_queue add constraint add_queue_no_dupe_sites unique
> > (sites.url);
> >
On Wed, 29 Jan 2003, Rodger Donaldson wrote:
> > On Tue, 28 Jan 2003, Rodger Donaldson wrote:
> >
> > > Now, adding a UNIQUE constraint on the pk for add_queue weeds out
> > > dupes there. However, attempting to add a cross-table UNIQUE check
> > > with:
> > >
> > > alter table add_queue add con
On Tue, 28 Jan 2003, Rodger Donaldson wrote:
> Now, adding a UNIQUE constraint on the pk for add_queue weeds out
> dupes there. However, attempting to add a cross-table UNIQUE check
> with:
>
> alter table add_queue add constraint add_queue_no_dupe_sites unique
> (sites.url);
> ERROR: parser: p
The problem: I have two tables, add_queue and sites, on a postgresql
7.2.x database. add_queue is where items go to be reviewed by a human
before being moved into sites. One of the things I'd like to do is to
cut down on the amount of work done by humans filtering out dupes and
sundry other prob
