Hi,
On Fri, 2016-11-11 at 15:30 -0700, StanC wrote:
> I tried 1.1 out.
Thanks for testing. We did not "announce" the packages yet, which means WIP. ;)
For the records, the package name also changed. Please wait until we finish
working on them :)
> Before installing I removed all traces of pre
I tried 1.1 out. Before installing I removed all traces of previous
pgadmin4 web and desktop.
It initially would not launch because the desktop file still pointed to
1.0. Easy to fix to point to 1.1.
It still fails to launch.
And, now the web app does not work.
Possibly some simple init thing I
Hello, Dave and pgadmin team!
I would like to present my fork of pgadmin3.
What's new:
1. Support PostgreSQL 9.6
2. Showing Access Methods (can't be edittable in SQL)
3. Showing and editing RLS policy objects
4. Functional for editing Index options in Index's editing dialog
My fork located at:
Hi
On Fri, Nov 11, 2016 at 2:34 PM, Walter Nordmann wrote:
>
> Problems making pgadmin4
>
> /opt/install/postgresql/pgadmin4/pgadmin4-1.1/runtime$ qmake
> Project MESSAGE: Building for QT5+...
> Project MESSAGE: Building for Linux/Mac...
> Project MESSAGE: Using /usr/bin/python-config
> Project M
Hi dave,
Am 11.11.2016 um 14:17 schrieb Dave Page:a.
May be you should add an info about returned data in the debug log?
something like "77 lines received"
We've released the last ever version of pgAdmin III now, so that
change won't happen I'm afraid.
Yes, pgadmin3 is closed - talking about pg
On 2016-11-10 16:55, Dave Page wrote:
I've just pushed a final wrap-up build of pgAdmin III to the download
site in source, Windows and Mac OS X formats. You can download it from
here:
https://www.postgresql.org/ftp/pgadmin3/release/v1.22.2/
This will be the final official release of pgAdmin I
Hi
On Fri, Nov 11, 2016 at 1:14 PM, Walter Nordmann wrote:
> Hi dave,
>
> INFO : 18:54:15: Running a DEBUG build.
>
> and that is only output if the build was done with the WXDEBUG flag set. It
> shouldn't make any difference here, but isn't the norm
>
> Really strange - but that should not be
Hi dave,
INFO : 18:54:15: Running a DEBUG build.
and that is only output if the build was done with the WXDEBUG flag
set. It shouldn't make any difference here, but isn't the norm
Really strange - but that should not be the problem.
in the log i can't see any result for queries excep
