On 5/07/2012 3:57 AM, Guillaume Lelarge wrote:
On Tue, 2012-07-03 at 14:50 +0800, Rohan Carly wrote:
On 17/02/2012 6:33 AM, Guillaume Lelarge wrote:
On Wed, 2012-02-15 at 05:16 -0600, Michael Shapiro wrote:
I have taken to making a copy of the password file so that when the
connection fails an
That's exactly why it does it.
On Thursday, July 5, 2012, Michael Shapiro wrote:
> I ran into this and the behavior actually make some sense -- PgAdmin can't
> know why the connection was rejected so it has to deal with the possibility
> that the stored might be wrong. One idea is for PgAdmin to
I ran into this and the behavior actually make some sense -- PgAdmin can't
know why the connection was rejected so it has to deal with the possibility
that the stored might be wrong. One idea is for PgAdmin to give an option
of either reconnecting using the stored password or to enter a new one.
On 5/07/2012 3:57 AM, Guillaume Lelarge wrote:
On Tue, 2012-07-03 at 14:50 +0800, Rohan Carly wrote:
On 17/02/2012 6:33 AM, Guillaume Lelarge wrote:
On Wed, 2012-02-15 at 05:16 -0600, Michael Shapiro wrote:
I have taken to making a copy of the password file so that when the
connection fails an
On Tue, 2012-07-03 at 14:50 +0800, Rohan Carly wrote:
> On 17/02/2012 6:33 AM, Guillaume Lelarge wrote:
> > On Wed, 2012-02-15 at 05:16 -0600, Michael Shapiro wrote:
> >> I have taken to making a copy of the password file so that when the
> >> connection fails and PgAdmin removes the password, I ca
On Tue, 2012-07-03 at 10:05 +0200, Michał Sienicki wrote:
> Bug report - pgAdmin 1.14.3, Windows
>
> Trigger definition is not shown properly when function contains "empty"
> arguments.
>
> Example
>
> Trigger definition:
>
> CREATE TRIGGER test_trigger
> BEFORE INSERT
> ON test_table
> FOR EA
