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 1tfOKa-0025PF-DO for pgsql-general@arkaria.postgresql.org; Tue, 04 Feb 2025 19:11:32 +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 1tfOKY-007T5h-GF for pgsql-general@arkaria.postgresql.org; Tue, 04 Feb 2025 19:11:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tfOKY-007T5Z-5C for pgsql-general@lists.postgresql.org; Tue, 04 Feb 2025 19:11:30 +0000 Received: from mail-oi1-x22d.google.com ([2607:f8b0:4864:20::22d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tfOKV-003HuO-1G for pgsql-general@postgresql.org; Tue, 04 Feb 2025 19:11:29 +0000 Received: by mail-oi1-x22d.google.com with SMTP id 5614622812f47-3eb8db8ae9aso2502397b6e.1 for ; Tue, 04 Feb 2025 11:11:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738696286; x=1739301086; darn=postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+Fc2zzdggWdmtrDpP1sRHx+BkuCP+NR22kf+OfqEmpY=; b=dPq8UL7Av9gZ+mg+2GrLeM9jay/1T0JHQ2KxVI/b2jX6hUKNYMeT/yxchvM978ynKN n/gcAi/vPeTwBpHWmZVXwFiSRedryGiXarNseZf5fvt9ebh1wssVxZHhZj6ET8WDWpMg +1StAfJLVeXr0IGXPttYsFt5m0Y+RF6azb7DEjAY9c1hTZRvvuCglPUt+tgq3EXRwA0b rCZ+SjF3b+P2v9K+1HqWs0+N0T7dGVQ66T2cScvYBMRN8lYSA2lNEr79ZpUMZ14ot5is /vPp9Ii3fK+Cc9raX4ZqJ295p1GIp67bo20EjnbpN1EFz2ZUiwA8n+4yfYWdoEq3kZ2e WGRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738696286; x=1739301086; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+Fc2zzdggWdmtrDpP1sRHx+BkuCP+NR22kf+OfqEmpY=; b=ZORXg8bMfXkauF2Jxr/UVwSehpi78CaLdckVxW2F7bttQd4ByC475QPU+kFmYrBOi5 EApN+7CB0eDCz+czKzGbZv63yR30UNoOhyvEyVYtF6egXlT9O6aYzaZHGuRGjRjVrPBg PbfgqIAddh8GLmWOZ47l4LpgswApNxJ23v9xZFLIVH1/FT/a8vGp06ZJetlfnO9ny7QY 1bK7Yp1NLlYsJX42SfSA5DM1Um/ZplkfTYr+p8V29RVH6itN4tXf33oBj/daqWVqHz/E U55zYOZa4hxY4WT8iViRKD1i5Ne6Ccz63oBve8CrdHEidKqOHIlI8QOUxVZ1xhCEeBms zs9w== X-Gm-Message-State: AOJu0Yz6kv0ppe6i54eddZfSHR3kgv4ghc8Y/C8KYfOtcEKQLueV+RxX z0hmGJQWI/NioXjTjyOxHo7RTdOjn3HuhoTWaeXtUmJETT9ry52mptayKYcSszSmcsJ+TVvze/X 0ilBdTNIYFl2STnEICGSCGgtdOy6eDA== X-Gm-Gg: ASbGncuLzMkNAebPlLdWp1xeJm0C06K3Ezt3+F0SzfLmy+2VKJWbktXMJzpBnxs19mu frB6Wz9mg1intDd/cFo51zSEyQbA2yihSudqN6jcmSYVCforx2Yk3qePo0LM8p47z6xTSsSE= X-Google-Smtp-Source: AGHT+IEPvMJ8w2YSgptdXWMaky3nAqLdMwZw4t5o4aYbdrztAIdyg0wgAbEhT0SgxM1PK3kRICRPSSPGi/wvwc7wqng= X-Received: by 2002:a05:6808:ec8:b0:3ea:5161:f71 with SMTP id 5614622812f47-3f323a74353mr19014022b6e.20.1738696285917; Tue, 04 Feb 2025 11:11:25 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a05:6802:a0c:b0:577:9519:f64a with HTTP; Tue, 4 Feb 2025 11:11:25 -0800 (PST) In-Reply-To: <4c55f93-bff-a452-69da-6db5a5a33b33@appl-ecosys.com> References: <4e7a338-c7d3-e944-20bd-a6e346e175c7@appl-ecosys.com> <0def87f9-6fa6-49a7-b0bc-f313c066d387@gmail.com> <4c55f93-bff-a452-69da-6db5a5a33b33@appl-ecosys.com> From: "David G. Johnston" Date: Tue, 4 Feb 2025 12:11:25 -0700 X-Gm-Features: AWEUYZmE12OcjmA3kZzOasJH6uFeQoEnGCAzvapLM-yYZYOJ0tpvDvh9mjmDpKE Message-ID: Subject: Re: Lookup tables To: Rich Shepard Cc: "pgsql-general@postgresql.org" Content-Type: multipart/alternative; boundary="0000000000007e9cbc062d55c611" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007e9cbc062d55c611 Content-Type: text/plain; charset="UTF-8" On Tuesday, February 4, 2025, Rich Shepard wrote: > > I want to replace the old lookup table (with no FK) with this one. > Is the use of FK here intentional or a typo? Because everything written so far leads me to believe it should be PK. Pri,are key is the unique side, Foreign key is the usage side. David J. --0000000000007e9cbc062d55c611 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tuesday, February 4, 2025, Rich Shepard <rshepard@appl-ecosys.com> wrote:

I want to replace the old lookup table (with no FK) with this one.

Is the use of FK here intentional or a typ= o?=C2=A0 Because everything written so far leads me to believe it should be= PK.=C2=A0 Pri,are key is the unique side, Foreign key is the usage side.

David J.
--0000000000007e9cbc062d55c611--