20.08.2016 1:15, Stephen Cook:
On 2016-08-19 16:14, Patrick Headley wrote:
While not saying you should do so forever it would be nice to get some
bugs fixed in pgAdmin III since pgAdmin 4 is not ready for production
use yet.
And especially since pgAdmin3 has become unstable in the last few
rel
You are missing a "g" in "postgresql.org"
On Friday, August 19, 2016, Tom Kincaid wrote:
>
> Final-Recipient: RFC822; pgadmin-hackers-requ...@postresql.org
>
>
>
David J.
Hello all,
I was able to sign up for pgadmin-hackers by sending e-mail to
pgadmin-hackers-request with the text "subscribe" in the subject line.
However, when my son attempts to do it, he keeps getting the message
below. Thoughts on what he may be doing wrong or if there is an issue
with the major
On 2016-08-19 16:14, Patrick Headley wrote:
> While not saying you should do so forever it would be nice to get some
> bugs fixed in pgAdmin III since pgAdmin 4 is not ready for production
> use yet.
And especially since pgAdmin3 has become unstable in the last few
releases (OS X mainly but some W
I'd like to gently suggest here that Patrick makes a valid point. At least
perhaps roll up the commits made since February into a final release?
I don't think anyone's suggesting that pgAdmin III have parallel
development or long-term support, but the installed base is substantial.
On Fri, Aug 1
Dave,
I know you keep saying that you aren't planning any future updates of
pgAdmin III but I and several other users have requested that you do.
While not saying you should do so forever it would be nice to get some
bugs fixed in pgAdmin III since pgAdmin 4 is not ready for production
use ye
Hi
We're not planning any further pgAdmin III releases I'm afraid.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK:http://www.enterprisedb.com
The Enterprise PostgreSQL Company
> On 19 Aug 2016, at 19:00, Hibbard, Brandon
> wrote:
>
> Hello,
>
> Is there a
Hello,
Is there a timeline of when pgadmin III version 1.22.2 will be released? There
is a bug that was fixed in version 1.22.2 in February that causes everyone at
my company problems. It would be great to have it released soon.
Thanks for all your work,
Brandon
