From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Yosry Muhammad <yosrym93(at)gmail(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: [Help] Modifying get_columns.sql template |
Date: | 2019-08-02 08:01:39 |
Message-ID: | CA+OCxoygyrcSeFhL_+KWNaR50VqPqka5Es=6Mq07XNLOJd3CrA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Yosry,
On Fri, Aug 2, 2019 at 7:51 AM Yosry Muhammad <yosrym93(at)gmail(dot)com> wrote:
> Hi hackers!
>
> I was wondering if modifying the query in: get_columns.sql @
> pgadmin/tools/sqleditor/templates/sql/default/
> to also SELECT attnum (attribute number) in addition to the already
> SELECTed columns will break any code or tests?
>
It shouldn't, as the code shouldn't be dependent on column ordering (if it
is, I consider that a bug). Adding it at the end of the select list would
be safest of course.
>
> I know this template is used in multiple places throughout the code and
> tests and I don't completely understand all the parts it is used in.
>
> Can someone guide in terms of whether or not this will break anything? If
> so, what parts of the code do I need to update?
>
Well we have tests, so make your changes and see if anything breaks :-).
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2019-08-02 09:25:25 | pgAdmin 4 commit: Use the full tab space for CodeMirror instances on di |
Previous Message | Yosry Muhammad | 2019-08-02 06:51:05 | [Help] Modifying get_columns.sql template |