Re: pgAdmin 4.3 scratch pad

[Cherio]

This would be a great option to have. Scratchpad can be a nuisance
especially due to resizing bug. For some reason nomatter how you resize
results panel scratchpad grows in size.

On Tue, Mar 19, 2019 at 11:36 AM richard coleman <
rcoleman.ascen...@gmail.com> wrote:

> Hi All,
>
> Is there a setting to *stop* the scratch pad from showing up *every time *you
> open a query window?
>
> pgAdmin 4.3, Kubuntu 18.10, Chromium
>
> Thanks,
>
> rik.
>

Re: Noisy dependency on psycopg2 versus psycopg2-binary

[Dave Page]

On Tue, Mar 19, 2019 at 1:37 PM Shaheed Haque  wrote:

> On Tue, 19 Mar 2019 at 10:28, Dave Page  wrote:
>
>> Hi
>>
>> On Tue, Mar 19, 2019 at 10:19 AM Shaheed Haque 
>> wrote:
>>
>>> Hi,
>>>
>>> I'm still on 4.2, but checking the release notes for 4.3 suggests it too
>>> has the problem of being dependent on psycopg2 versus psycopg2-binary. This
>>> results in the annoying message:
>>>
>>> /usr/local/lib/python3.6/dist-packages/psycopg2/__init__.py:144:
 UserWarning: The psycopg2 wheel package will be renamed from release 2.8;
 in order to keep installing from binary please use "pip install
 psycopg2-binary" instead. For details see: <
 http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>.

>>>
>>> My package also had this problem, and the fix was to replace the
>>> reference to psycopg2 with  psycopg2-binary in setup.py. I hope that helps,
>>>
>>
>> This is not a problem for us - it's completely intentional. We need full
>> control over the build of psycopg2, so we can ensure that it, and the
>> libpq, OpenSSL, Gettext and other dependent libraries as well as our
>> runtime and Python build are all using the same compiler and compiler flags
>> etc.
>>
>
> That makes sense.
>
>
>> If there's a way that we could conditionally use psycopg2-binary *just*
>> for the wheel, I'd be open to that, but I'm not sure how we could do it.
>>
>
> OK, I can see that might be tricky. What, if anything, can I as an
> end-user (i.e. someone wanting as little in the way of source builds as
> possible :-)) do to avoid the warning? For example, if I were to "pip3
> install --upgrade psycopg2-binary" after the install of pgadmin4, would
> that be a reasonable/supported thing to do to get rid of the warning? Or
> would I end up with some horrendous/confusing mess?
>
> Thanks, Shaheed
>
> P.S. I should perhaps explain that we have quite a few Bash and Python
> scripts that end up indirectly importing the package, and thus our log
> files are sprinkled with these messages...
>

I had a brainwave. Aditya, Khushboo - do you see any reason why we couldn't
do the attached?

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

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


psycopg2-binary.diff
Description: Binary data

pgAdmin 4.3 scratch pad

[richard coleman]

Hi All,

Is there a setting to *stop* the scratch pad from showing up *every time *you
open a query window?

pgAdmin 4.3, Kubuntu 18.10, Chromium

Thanks,

rik.

Re: Noisy dependency on psycopg2 versus psycopg2-binary

[Shaheed Haque]

On Tue, 19 Mar 2019 at 10:28, Dave Page  wrote:

> Hi
>
> On Tue, Mar 19, 2019 at 10:19 AM Shaheed Haque  wrote:
>
>> Hi,
>>
>> I'm still on 4.2, but checking the release notes for 4.3 suggests it too
>> has the problem of being dependent on psycopg2 versus psycopg2-binary. This
>> results in the annoying message:
>>
>> /usr/local/lib/python3.6/dist-packages/psycopg2/__init__.py:144:
>>> UserWarning: The psycopg2 wheel package will be renamed from release 2.8;
>>> in order to keep installing from binary please use "pip install
>>> psycopg2-binary" instead. For details see: <
>>> http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>.
>>>
>>
>> My package also had this problem, and the fix was to replace the
>> reference to psycopg2 with  psycopg2-binary in setup.py. I hope that helps,
>>
>
> This is not a problem for us - it's completely intentional. We need full
> control over the build of psycopg2, so we can ensure that it, and the
> libpq, OpenSSL, Gettext and other dependent libraries as well as our
> runtime and Python build are all using the same compiler and compiler flags
> etc.
>

That makes sense.


> If there's a way that we could conditionally use psycopg2-binary *just*
> for the wheel, I'd be open to that, but I'm not sure how we could do it.
>

OK, I can see that might be tricky. What, if anything, can I as an end-user
(i.e. someone wanting as little in the way of source builds as possible
:-)) do to avoid the warning? For example, if I were to "pip3 install
--upgrade psycopg2-binary" after the install of pgadmin4, would that be a
reasonable/supported thing to do to get rid of the warning? Or would I end
up with some horrendous/confusing mess?

Thanks, Shaheed

P.S. I should perhaps explain that we have quite a few Bash and Python
scripts that end up indirectly importing the package, and thus our log
files are sprinkled with these messages...





>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

RE: pgadmin 4 missing features

[Polgár Benedek]



Thank you very much! It’s working!

Best Regards, Benedek!

From: Dave Page 
Sent: Tuesday, March 19, 2019 12:55 PM
To: Polgár Benedek 
Cc: pgadmin-support@lists.postgresql.org
Subject: Re: pgadmin 4 missing features

Hi

On Tue, Mar 19, 2019 at 11:47 AM Polgár Benedek 
mailto:polgar.bene...@otpmobil.com>> wrote:
Hi!
Thank you so much!

It's not clear to me at the port number settings.
Which tray icon should I click? I can't find the "Fixed Port Number?" option.

Can you send a screenshot?


See attached (this is on a Mac, but it's all roughly the same on other 
platforms)...


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

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

RE: pgadmin 4 missing features

[Polgár Benedek]

Hi!
Thank you so much!

It's not clear to me at the port number settings.
Which tray icon should I click? I can't find the "Fixed Port Number?" option.

Can you send a screenshot?

__
Best Regards: Benedek Polgár | System administrator | 
polgar.bene...@otpmobil.com

From: Dave Page 
Sent: Tuesday, March 19, 2019 11:34 AM
To: Polgár Benedek 
Cc: pgadmin-support@lists.postgresql.org
Subject: Re: pgadmin 4 missing features

Hi

On Tue, Mar 19, 2019 at 10:19 AM Polgár Benedek 
mailto:polgar.bene...@otpmobil.com>> wrote:
Dear Support Teams!

I miss the „Favourites” and global history file features in pgAdmin 4 version. 
These features is in pgAdmin 3 and I would like use these in pgAdmin 4 too.

4.4 (when released) has persistent query history, tied to the pgAdmin user and 
the database. There are no current plans to make that history global.

Favourites is really just a different way to save/load queries (it just stores 
them elsewhere). I would suggest simply saving favourite queries and loading 
them as needed - it's basically the same workflow, but also allows you to use 
other editors should you wish, or to pipe into psql etc.


A pgAdmin 4 uses random ports, so i can’t create Chrome shortcut for this. I 
would like to I can set fix port number to pgAdmin4

You can set a fixed port number - click the tray icon and select Configure from 
the menu, then check the "Fixed Port Number?" option and select the port you 
want to use.

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

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

Re: pgadmin 4 missing features

[Dave Page]

Hi

On Tue, Mar 19, 2019 at 10:19 AM Polgár Benedek 
wrote:

> Dear Support Teams!
>
>
>
> I miss the „Favourites” and global history file features in pgAdmin 4
> version. These features is in pgAdmin 3 and I would like use these in
> pgAdmin 4 too.
>

4.4 (when released) has persistent query history, tied to the pgAdmin user
and the database. There are no current plans to make that history global.

Favourites is really just a different way to save/load queries (it just
stores them elsewhere). I would suggest simply saving favourite queries and
loading them as needed - it's basically the same workflow, but also allows
you to use other editors should you wish, or to pipe into psql etc.


>
>
> A pgAdmin 4 uses random ports, so i can’t create Chrome shortcut for this.
> I would like to I can set fix port number to pgAdmin4
>

You can set a fixed port number - click the tray icon and select Configure
from the menu, then check the "Fixed Port Number?" option and select the
port you want to use.

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

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

Re: Noisy dependency on psycopg2 versus psycopg2-binary

[Dave Page]

Hi

On Tue, Mar 19, 2019 at 10:19 AM Shaheed Haque  wrote:

> Hi,
>
> I'm still on 4.2, but checking the release notes for 4.3 suggests it too
> has the problem of being dependent on psycopg2 versus psycopg2-binary. This
> results in the annoying message:
>
> /usr/local/lib/python3.6/dist-packages/psycopg2/__init__.py:144:
>> UserWarning: The psycopg2 wheel package will be renamed from release 2.8;
>> in order to keep installing from binary please use "pip install
>> psycopg2-binary" instead. For details see: <
>> http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>.
>>
>
> My package also had this problem, and the fix was to replace the reference
> to psycopg2 with  psycopg2-binary in setup.py. I hope that helps,
>

This is not a problem for us - it's completely intentional. We need full
control over the build of psycopg2, so we can ensure that it, and the
libpq, OpenSSL, Gettext and other dependent libraries as well as our
runtime and Python build are all using the same compiler and compiler flags
etc.

If there's a way that we could conditionally use psycopg2-binary *just* for
the wheel, I'd be open to that, but I'm not sure how we could do it.

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

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

Noisy dependency on psycopg2 versus psycopg2-binary

[Shaheed Haque]

Hi,

I'm still on 4.2, but checking the release notes for 4.3 suggests it too
has the problem of being dependent on psycopg2 versus psycopg2-binary. This
results in the annoying message:

/usr/local/lib/python3.6/dist-packages/psycopg2/__init__.py:144:
> UserWarning: The psycopg2 wheel package will be renamed from release 2.8;
> in order to keep installing from binary please use "pip install
> psycopg2-binary" instead. For details see: <
> http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>.
>

My package also had this problem, and the fix was to replace the reference
to psycopg2 with  psycopg2-binary in setup.py. I hope that helps,

Thanks, Shaheed

pgadmin 4 missing features

[Polgár Benedek]

Dear Support Teams!

I miss the "Favourites" and global history file features in pgAdmin 4 version. 
These features is in pgAdmin 3 and I would like use these in pgAdmin 4 too.

A pgAdmin 4 uses random ports, so i can't create Chrome shortcut for this. I 
would like to I can set fix port number to pgAdmin4

Can you solve these?
Thanks in advance!
__
Best Regardsl:

Benedek Polgár
System administrator

polgar.bene...@otpmobil.com

[cid:image001.png@01CF9768.53366360]

1093 Budapest, Közraktár u. 30-32.
RiverPark, K30. épület, II. emelet

[cid:image002.png@01D100FE.9034AF00]
  [cid:image003.png@01D100FE.9034AF00]