| From: | Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Lookup tables |
| Date: | 2025-02-04 19:03:27 |
| Message-ID: | dcc1d1bd-8ec5-4ec9-b3c7-a67889c6034d@gelassene-pferde.biz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-general |
04.02.2025 18:31:09 Michał Kłeczek <michal(at)kleczek(dot)org>:
>> Unless the lookup table is actually a check constraint one can use to populate dropdown boxes in an interface.
>
> That is even worse because it ceases being transactional and users might select something different than what they see on the screen.
In how far is a real check constraint less transactional? And in how far is it more advisable to have a real check constraint and fill your dropdown boxes from another source and having to keep that source on sync with the real check constraint?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Krishnendu Dasgupta | 2025-02-04 19:05:53 | PGAdmin Desktop Docker Setup |
| Previous Message | David G. Johnston | 2025-02-04 18:20:53 | Re: Lookup tables |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2025-02-04 19:08:42 | Re: Lookup tables |
| Previous Message | David G. Johnston | 2025-02-04 19:00:38 | Re: Understanding ALTER DEFAULT PRIVILEGES Behavior in PostgreSQL |