Re: Thoughts on a cosntraint ?

From: Rob Sargent <robjsargent(at)gmail(dot)com>
To: John W Higgins <wishdev(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Thoughts on a cosntraint ?
Date: 2019-09-29 20:41:57
Message-ID: F01FBE40-A1DD-49B7-9C73-7ECA4F987E76@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Sep 29, 2019, at 1:52 PM, John W Higgins <wishdev(at)gmail(dot)com> wrote:
>
> On Sun, Sep 29, 2019 at 12:40 PM stan <stanb(at)panix(dot)com <mailto:stanb(at)panix(dot)com>> wrote:
> I have a table that consists of 3 columns.
>
> vendor_key
> mfg_key
> preferred (boolean)
>
> The idea is that a given vendor is the vendor we want to use for each
> manufacturer for a given project.
>
> I need to constrain such that only on row of mfg, vendor and project can
> be set to TRUE.
>
>
> Partial unique index
>
> Example 3 on this page https://www.postgresql.org/docs/current/indexes-partial.html <https://www.postgresql.org/docs/current/indexes-partial.html> is exactly what you are looking for.
>
> John W Higgins
>
Yes but I have to wonder about one-and-only-one preferred vendor: if there are many known, acceptable vendors, wouldn’t a ranking be more useful? On a crucial commodity it is common practice to continuously use more than one vendor (i.e. multiple preferred vendors).

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2019-09-29 21:16:50 Re: Thoughts on a cosntraint ?
Previous Message John W Higgins 2019-09-29 19:52:50 Re: Thoughts on a cosntraint ?