MIME-Version: 1.0
References: <4e7a338-c7d3-e944-20bd-a6e346e175c7@appl-ecosys.com>
In-Reply-To: <4e7a338-c7d3-e944-20bd-a6e346e175c7@appl-ecosys.com>
From: Tony Shelver <tshelver@gmail.com>
Date: Tue, 4 Feb 2025 17:11:00 +0200
Message-ID: 
 <CAG0dhZBNiGSQ_hiRcMPP27z_1ZEiNadcgv0Ui5e34o26FQEv-A@mail.gmail.com>
Subject: Re: Lookup tables
To: Rich Shepard <rshepard@appl-ecosys.com>,
	"pgadmin-support lists.postgresql.org" <pgadmin-support@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000005dbe2c062d526b4d"
Archived-At: 
 <https://www.postgresql.org/message-id/CAG0dhZBNiGSQ_hiRcMPP27z_1ZEiNadcgv0Ui5e34o26FQEv-A%40mail.gmail.com>
Precedence: bulk

--0000000000005dbe2c062d526b4d
Content-Type: text/plain; charset="UTF-8"

Seen the suggestions.

After decades of playing with the alternatives, I don't overthink it
anymore.  Pretty much my lookup tables consist of an autogenerated primary
key (smallint or integer), a code (name?) and a description as default.

If there are a lot of tables fitting a common  data format, at times I have
consolidated them into a single table with a 'lookup type' column.

Depending on application requirements, sometimes there I will provide short
and long display names, and a generic description for further
clarification, but usually those requirements are overkill.

Tony

On Tue, 4 Feb 2025 at 16:28, Rich Shepard <rshepard@appl-ecosys.com> wrote:

> Should lookup tables have a numeric FK column as well as the description
> column?
>
> If so, how should I add an FK to the two lookup tables in my database?
>
> TIA,
>
> Rich
>
>
>

--0000000000005dbe2c062d526b4d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Seen the suggestions.</div><div><br></div><div>After =
decades of playing with the alternatives, I don&#39;t overthink it anymore.=
=C2=A0 Pretty much my lookup tables consist of an autogenerated primary key=
 (smallint or integer), a code (name?) and a description as default.=C2=A0 =
<br></div><div><br></div><div>If there are a lot of tables fitting a common=
=C2=A0 data format, at times I have consolidated them into a single table w=
ith a &#39;lookup type&#39; column.=C2=A0 <br></div><div><br></div><div>Dep=
ending on application requirements, sometimes there I will provide short an=
d long display names, and a generic description for further clarification, =
but usually those requirements are overkill.</div><div><br></div><div>Tony<=
br></div></div><br><div class=3D"gmail_quote gmail_quote_container"><div di=
r=3D"ltr" class=3D"gmail_attr">On Tue, 4 Feb 2025 at 16:28, Rich Shepard &l=
t;<a href=3D"mailto:rshepard@appl-ecosys.com">rshepard@appl-ecosys.com</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Shoul=
d lookup tables have a numeric FK column as well as the description column?=
<br>
<br>
If so, how should I add an FK to the two lookup tables in my database?<br>
<br>
TIA,<br>
<br>
Rich<br>
<br>
<br>
</blockquote></div>

--0000000000005dbe2c062d526b4d--