Received-SPF: pass (ha01s018.org-dns.com: connection is authenticated)
Message-ID: <f2e0f8dd-172a-4522-95c7-e107e05593e5@gelassene-pferde.biz>
Date: Wed, 5 Feb 2025 21:15:41 +0100
MIME-Version: 1.0
Subject: Re: Lookup tables
To: pgsql-general@lists.postgresql.org
References: <Z6JFgsSGF_kM4yLE@hermes.hilbert.loc>
 <6DCD3899-51A8-4032-A189-F2B51AD7CC8F@kleczek.org>
 <c77aae45-5914-4973-8d32-9b6efa6545d9@gelassene-pferde.biz>
 <4B983ADC-3A5C-442F-B377-D0C10FC1C100@kleczek.org>
Content-Language: de-CH-frami, en-GB, it-CH, fr-CH, es-CL, es-ES
From: Thiemo Kellner <thiemo@gelassene-pferde.biz>
In-Reply-To: <4B983ADC-3A5C-442F-B377-D0C10FC1C100@kleczek.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/f2e0f8dd-172a-4522-95c7-e107e05593e5%40gelassene-pferde.biz>
Precedence: bulk


El 05-02-25 a las 19:13, Michał Kłeczek escribió:
>> Only if you do not see the primary key as the main immutable value identifying an object, entity, you name it.
> Surrogate key cannot identify any (real) object by definition :)
> What object is identified by PK value 42 in “restaurants” table?
What object is identified by a PK value "löasidfhaösliw" in a restaurant 
table? It is the context only giving it sense and not less sense then 42 
or "Pizza Hut". In fact on disk, you won't even find 42 or "Pizza Hut". 
On hard disks, e.g., it is the direction of a magnetic field of several 
locations on the disk. Btw, 42 seems to me a quite geeky name for a nerd 
restaurant.
>> Having said that, it is very questionable that a natural key (names to name one) can be a suitable primary key (think of typo).
> Typos are indeed a problem but adding surrogate key does not solve it, I’m afraid.
In how far does it not solve it? Or maybe better asked. Is your problem 
that typos occur or is the problem the amount of hassle to fix it?