Re: Lookup tables

David G. Johnston <david.g.johnston@gmail.com>

From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Date: 2025-02-04T15:04:54Z
Lists: pgsql-general
On Tuesday, February 4, 2025, Ron Johnson <ronljohnsonjr@gmail.com> wrote:

> On Tue, Feb 4, 2025 at 9:28 AM Rich Shepard <rshepard@appl-ecosys.com>
> wrote:
>
>> Should lookup tables have a numeric FK column as well as the description
>> column?
>>
>
> Does your lookup table just have one column?  (That's what your question
> seems to imply, but that makes no sense, since the whole point of a lookup
> table is to store some sort of a code in the "child" table instead of the
> whole text of the description.)
>

The point of a lookup table is to provide a unique list of authoritative
values for some purpose.  Kinda like an enum.  But having the label serve
as the unique value is reasonable - we only add surrogates for optimization.

David J.