From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | dan d <dano2k3(at)hotmail(dot)com> |
Cc: | Euler Taveira <euler(at)timbira(dot)com(dot)br>, "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Doc BUG and/or Change Request: Include Postgres's system columns in reserved words in docs, Chnage to previx sytem colums with 2 underscores? |
Date: | 2017-10-03 17:57:11 |
Message-ID: | CAKFQuwY=Vntgyo3wvsZpt8p3ixkVGC+VCu_Df15_qR=L6w7e5Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Tue, Oct 3, 2017 at 10:34 AM, dan d <dano2k3(at)hotmail(dot)com> wrote:
> The fix is really simply prefix system reserved column names with one or
> two underscores. Simple clean prevents the issue between user code and
> database code...
>
The challenge isn't in making the fix (though it would likely be extremely
tedious). The challenge is compatibility given the the current state has
been in place for decades; system columns are user-visible.
This seems like a case where the cure is potentially worse than the
disease. It is difficult to please everyone and since this particular
problem is very end-user specific whereas a change would impact many
perfectly fine applications it seems like displeasing the unique end-user
(and thus retain the status quo) is likely to prevail even were someone to
invest the time to write a patch. Though, unless someone is seriously
offering to write such a patch wondering whether it would be accepted is
not particularly productive.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | devguy.ca | 2017-10-03 19:38:04 | inappropriate word 'victim' |
Previous Message | dan d | 2017-10-03 17:34:21 | Re: Doc BUG and/or Change Request: Include Postgres's system columns in reserved words in docs, Chnage to previx sytem colums with 2 underscores? |