| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Michał Kłeczek <michal(at)kleczek(dot)org> |
| Cc: | Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Lookup tables |
| Date: | 2025-02-04 18:20:53 |
| Message-ID: | CAKFQuwYKGwnQpRSz0Hep3OTG-WXAn0RpPAKL1wsz2dcp9K=ELA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-general |
On Tuesday, February 4, 2025, Michał Kłeczek <michal(at)kleczek(dot)org> wrote:
>
> > On 4 Feb 2025, at 18:27, Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz>
> wrote:
> >
> > 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.
>
What is the process flow for this happening? How big a bug needs to exist
in the system for something bad to happen as opposed to some kind of “value
not found” error and a refresh with the correct matching values showing up
in the UI?
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thiemo Kellner | 2025-02-04 19:03:27 | Re: Lookup tables |
| Previous Message | Karsten Hilbert | 2025-02-04 17:52:34 | Re: Lookup tables |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ayush Vatsa | 2025-02-04 18:49:56 | Understanding ALTER DEFAULT PRIVILEGES Behavior in PostgreSQL |
| Previous Message | Adrian Klaver | 2025-02-04 18:06:55 | Re: old OS |