pgAdmin 4 commit: Ensure we create a DMG file that's compatible with ma

[Dave Page]

Ensure we create a DMG file that's compatible with macOS 10.10+

Branch
--
master

Details
---
https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=1a192109d62a8bc84ec44388ece94eff70db530a

Modified Files
--
pkg/mac/create-dmg.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

New macOS Build

[Dave Page]

Hi Fahar,

I've stood up a new macOS build server (as the old one is getting
unreliable). Can you please test the build at
https://developer.pgadmin.org/builds/2019-04-15-macos2-test2/? Please
remember to test the file dialogue and external processes as those are the
places most likely to be affected (everything else is likely to be fine if
we can connect to the database, browse the schema and run queries).

All;

It seems that supporting macOS < 10.12 (Sierra) is somewhat hard now, as Qt
have dropped support for it, and Apple also seem to be using that as a
compatibility break version. Does anyone see any major reason why we can't
require 10.12 or later for pgAdmin?

Note that I've already updated the website to say we only support 10.12+.
For now though, that's just meant as "discouragement" rather than a hard
and fast rule.

Thanks.

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

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: New macOS Build

[Fahar Abbas]

Hi Dave,


On Mon, Apr 15, 2019 at 4:39 PM Dave Page  wrote:

> Hi Fahar,
>
> I've stood up a new macOS build server (as the old one is getting
> unreliable). Can you please test the build at
> https://developer.pgadmin.org/builds/2019-04-15-macos2-test2/? Please
> remember to test the file dialogue and external processes as those are the
> places most likely to be affected (everything else is likely to be fine if
> we can connect to the database, browse the schema and run queries).
>
> I have already performed the smoke verification on MAC 10.12, MAC 10.13
and MAC 10.14 and no issue found so while detail verification is in
progress.

All;
>
> It seems that supporting macOS < 10.12 (Sierra) is somewhat hard now, as
> Qt have dropped support for it, and Apple also seem to be using that as a
> compatibility break version. Does anyone see any major reason why we can't
> require 10.12 or later for pgAdmin?
>
> Note that I've already updated the website to say we only support 10.12+.
> For now though, that's just meant as "discouragement" rather than a hard
> and fast rule.
>
> Thanks.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>


-- 
Fahar Abbas
QMG
EnterpriseDB Corporation
Phone Office: +92-51-835-8874
Phone Direct: +92-51-8466803
Mobile: +92-333-5409707
Skype ID: *live:fahar.abbas*
Website: www.enterprisedb.com

Re: New macOS Build

[Dave Page]

On Mon, Apr 15, 2019 at 1:43 PM Fahar Abbas 
wrote:

> Hi Dave,
>
>
> On Mon, Apr 15, 2019 at 4:39 PM Dave Page  wrote:
>
>> Hi Fahar,
>>
>> I've stood up a new macOS build server (as the old one is getting
>> unreliable). Can you please test the build at
>> https://developer.pgadmin.org/builds/2019-04-15-macos2-test2/? Please
>> remember to test the file dialogue and external processes as those are the
>> places most likely to be affected (everything else is likely to be fine if
>> we can connect to the database, browse the schema and run queries).
>>
>> I have already performed the smoke verification on MAC 10.12, MAC 10.13
> and MAC 10.14 and no issue found so while detail verification is in
> progress.
>

Great, thanks!


>
> All;
>>
>> It seems that supporting macOS < 10.12 (Sierra) is somewhat hard now, as
>> Qt have dropped support for it, and Apple also seem to be using that as a
>> compatibility break version. Does anyone see any major reason why we can't
>> require 10.12 or later for pgAdmin?
>>
>> Note that I've already updated the website to say we only support 10.12+.
>> For now though, that's just meant as "discouragement" rather than a hard
>> and fast rule.
>>
>> Thanks.
>>
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>
>
> --
> Fahar Abbas
> QMG
> EnterpriseDB Corporation
> Phone Office: +92-51-835-8874
> Phone Direct: +92-51-8466803
> Mobile: +92-333-5409707
> Skype ID: *live:fahar.abbas*
> Website: www.enterprisedb.com
>


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

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Disconnect user from

[Igor Miranda]

Hello,

I have a PostgreSQL cluster on a read replication topology and I want to 
know if it's possible to send commands to all replicas from the primary 
instance (in this particular case, it'd be to disconnect one user from 
all replicas).
I know it is possible to log into each and every replica and issue 
pg_terminate_backend, but this solution isn't feasible in our case...

Any idea would help a lot! Regards

--
Att,
Ajudici 

Igor Fernandes Miranda
*Desenvolvedor |*   Ajudici 

Tel.: (61) 992492816

Disconnect user from replica

[Igor Miranda]

Hello,

I have a PostgreSQL cluster on a read replication topology and I want to 
know if it's possible to send commands to all replicas from the primary 
instance (in this particular case, it'd be to disconnect one user from 
all replicas).
I know it is possible to log into each and every replica and issue 
pg_terminate_backend, but this solution isn't feasible in our case...

Any idea would help a lot! Regards

--
Att,
Ajudici 

Igor Fernandes Miranda
*Desenvolvedor |*   Ajudici 

Tel.: (61) 992492816

Re: [pgAdmin4][Patch] - RM 3605 & 2392 - View data fixes

[Khushboo Vashi]

Hi,

Please find the attached patch with some modification discussed at Redmine
for the RM #2392.

1. On deletion, strikeout the selected rows and delete those while clicking
on the Save button.
2. If only newly added rows are to be deleted then delete those directly.

Also, Slickgrid has been upgraded to the latest v2.3.4.

Thanks,
Khushboo

On Tue, Apr 9, 2019 at 11:46 AM Akshay Joshi 
wrote:

> Hi Khushboo
>
> Found some new issues:
>
>1. Delete button gets enabled if I select any new cell (type text) to
>enter some value.
>
> Fixed

>
>1. Add two new rows, don't click on Save button and delete couple of
>rows. Colour of newly added rows will changed to green.
>
> Not applicable now

>
>1. Create a table with Serial and Text column. Add two new rows,
>specify the values and don't click on Save button. Delete some rows and
>then click on Save button, data is saved in the database but grid is
>showing same serial id for two newly created rows. After re-run the query
>it shows the correct value.
>
> Fixed

> Can you please fix the above issues.
>
> On Mon, Apr 8, 2019 at 2:20 PM Khushboo Vashi <
> khushboo.va...@enterprisedb.com> wrote:
>
>> Hi,
>>
>> Please find the attached updated patch.
>>
>> Thanks,
>> Khushboo
>>
>> On Fri, Apr 5, 2019 at 11:32 AM Akshay Joshi <
>> akshay.jo...@enterprisedb.com> wrote:
>>
>>> Hi Khushboo
>>>
>>> #3605 is fixed and found below issue in #2392
>>>
>>>- As per steps given in RM, I have perform the same. But when I
>>>delete the row, delete button is still enabled and save button is 
>>> disabled
>>>even though newly created row is still there. Apart from that code looks
>>>good to me. Please fix it.
>>>
>>>
>>> Fixed.
>>
>>> On Thu, Apr 4, 2019 at 5:27 PM Khushboo Vashi <
>>> khushboo.va...@enterprisedb.com> wrote:
>>>
 Hi,

 Please find the attached patch to fix:

 1. #3605 - Edit Data: Deleting N number of rows makes first N number of
 rows disable
 2. #2392 - Datagrid: If we delete any row it also saves newly added row

 Thanks,
 Khushboo



>>>
>>> --
>>> *Thanks & Regards*
>>> *Akshay Joshi*
>>>
>>> *Sr. Software Architect*
>>> *EnterpriseDB Software India Private Limited*
>>> *Mobile: +91 976-788-8246*
>>>
>>
>
> --
> *Thanks & Regards*
> *Akshay Joshi*
>
> *Sr. Software Architect*
> *EnterpriseDB Software India Private Limited*
> *Mobile: +91 976-788-8246*
>


RM_3605_2392_v2.patch
Description: Binary data