Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tfKPD-001SJX-PT for pgsql-general@arkaria.postgresql.org; Tue, 04 Feb 2025 15:00:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tfKPC-004EGd-P1 for pgsql-general@arkaria.postgresql.org; Tue, 04 Feb 2025 15:00:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tfKPC-004EFZ-E5 for pgsql-general@lists.postgresql.org; Tue, 04 Feb 2025 15:00:02 +0000 Received: from mail-ot1-x329.google.com ([2607:f8b0:4864:20::329]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tfKPA-0038bB-0W for pgsql-general@postgresql.org; Tue, 04 Feb 2025 15:00:01 +0000 Received: by mail-ot1-x329.google.com with SMTP id 46e09a7af769-724d1724657so3270290a34.0 for ; Tue, 04 Feb 2025 07:00:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738681199; x=1739285999; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=e98BJKueYrF801IaR01dzLnBqxvX3gB6qSVCBtboe5I=; b=Dj1e1PItn7N3m+4f3y7F2MSRhxklp5k6Ce56kB9chCmN6dXcDtswFrhf4tKAnmGndt w4hlBoZmDMNiVUMSEMUNT5VTxiAdBwqpZmuSEBl9d6v4E/lZgMqbeH+22tKWkfS4kIlG 9E+GARRMafgEWV88dzZ12p+tNTRCeHYLtW4xGoyOLYivTnEgWQK9H66iimr+cv8gEBbE yLRVieFCaeB2FZpTRYhH0k3gLAyMrRPAUPg0kni+k1EcVg0FRWKqf7BI9Q92D1sNVqfu oYaiP5LdckLb/q9KI7QflVlQWKDVNp96ColdYEgTI/YqCv5onugThkujY4TFdJKwYz8p +ZrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738681199; x=1739285999; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=e98BJKueYrF801IaR01dzLnBqxvX3gB6qSVCBtboe5I=; b=oqCHJaTkUJ75tC7X0mzW8Ee6MMYrx7BZxNCS+VxKpRAMoQjw2KGzx0+fX/rAGvpWpT BCk6pEfvE5csYX5SvLK3GmP+KnibJulsWPhIvYDqiqlXMJ8pz7hFkn9iGQJaymn+Cbxp emD4yWFutWqTUckxnffFtDjhDBk99lD9wZ9iP1xvRjHxTOkKSX+lLmE8gTX0ly/2GGmF jqwM8gQ1rfbQ0JjtkWVuYVWScb8yRXYXBuQ5Mo/TnFc3zivK95lJ8SI4x5CAdPgB1jqz 3SjWvism2fm4DjHdfITG4CKa0OKu30x5+E2vQCqBbAS0mjFwRU0Kt4eVHQF7QVNWw063 AuMg== X-Gm-Message-State: AOJu0YxpR+l2elaX5WKiGdHT43zfOyqq8GJ9mMu2C1SrjWbXE3dLo/fi d4lYrDrGu2zXXgg+ropq5IA0F7A0QDivhEdx7PSb6BjhFPHhvJAQhNGYPGDRqsyo+qAfgeQacNE RXbwCQP3bce/7b3QmNG7SDPcq9qOi+g== X-Gm-Gg: ASbGncvlZyEbQOBB7gpc66hKZoAc0W5MJZluI6aeoYT5JesFv1hwXz6NonORJw7h48/ SroLoIWG1wTHYRLkVolxnmpnL335M1cyhmW5s5kpcfOuyecFryRF1YgFZc8WxJE+CqqvgB0oHcd N9KegyMCHVkpnVaV7aohsVm5UWeQeWFvs= X-Google-Smtp-Source: AGHT+IFOq5X94v1RgA0HbWs/9vw5qVlLwgrZqp9q9RIS6R3+/bH8L9akpGc4EwvV3g/9jvpFGv8tx9HTkanrItyb6F0= X-Received: by 2002:a05:6871:a9c3:b0:29f:b645:ce86 with SMTP id 586e51a60fabf-2b3e76d02e4mr2086636fac.12.1738681199578; Tue, 04 Feb 2025 06:59:59 -0800 (PST) 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: Ron Johnson Date: Tue, 4 Feb 2025 09:59:48 -0500 X-Gm-Features: AWEUYZnB3-AqhDjeyOCyQ0qK4e3KN88CS76aF8x0vZu-PIj8qtCp_DP35bUA2CY Message-ID: Subject: Re: Lookup tables To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000475731062d524388" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000475731062d524388 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Feb 4, 2025 at 9:28=E2=80=AFAM Rich Shepard 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.) --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000475731062d524388 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Feb 4, 2025 at 9:28=E2=80=AFAM Ri= ch Shepard <rshepard@appl-ec= osys.com> wrote:
Should lookup tables h= ave a numeric FK column as well as the description column?
=

Does your lookup table just have one column?=C2=A0 (Tha= t's what your question seems to imply, but that makes no sense, since t= he whole point of a lookup table is to store some sort of a code in the &qu= ot;child" table instead of the whole text of the description.)

--
Death to <Redac= ted>, and butter sauce.
Don't boil me, I'm still alive.
<= div>
<Redacted> lobster!
--000000000000475731062d524388--