Re: SQLAlchemy updates for check tables.

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com>
Cc: Nikhil Mohite <nikhil(dot)mohite(at)enterprisedb(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: SQLAlchemy updates for check tables.
Date: 2021-07-19 09:43:51
Message-ID: CA+OCxoxcT8u9VJPp_oEML0tL7D=sXFpy=jkFBz56K1ApQ=_Pfw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Mon, Jul 19, 2021 at 9:58 AM Khushboo Vashi <
khushboo(dot)vashi(at)enterprisedb(dot)com> wrote:

>
>
> On Mon, Jul 19, 2021 at 2:17 PM Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
>> Hi
>>
>> On Mon, Jul 19, 2021 at 6:37 AM Nikhil Mohite <
>> nikhil(dot)mohite(at)enterprisedb(dot)com> wrote:
>>
>>> Hi Hackers,
>>>
>>> Please find the attached patch for SQLAlchemy updates for check table is
>>> present in the database or not. (This will resolve load and dump server.)
>>>
>>
>> How come this upstream change didn't fail the regression tests?
>>
> Flask-SQLAlchemy is dependent on SQLAlchemy and which is an indirect
> dependency of pgAdmin, so if the installed version of Flask-SQLAlchemy is
> the latest one, it will be skipped.
>

Sure, but the regression test runs on the buildfarm build the venv from
scratch on every run (as happens when we build the packages themselves). So
I can see why local regression runs might have passed (as developers
generally don't recreate their venv's from scratch before testing), but I
would expect to have seen failures on the buildfarm.

--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake

EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Akshay Joshi 2021-07-19 12:22:36 Re: Bug #6337 Patch
Previous Message Khushboo Vashi 2021-07-19 08:57:59 Re: SQLAlchemy updates for check tables.