On Tue, Apr 7, 2009 at 5:11 PM, Mike Blackwell wrote:
> The quick search keys in the object browser window seem to operate a
> little differently. They will now search the children of the
> (unexpanded) currently selected node as well as the currently expanded
> nodes. I don't recall it doing th
The quick search keys in the object browser window seem to operate a
little differently. They will now search the children of the
(unexpanded) currently selected node as well as the currently expanded
nodes. I don't recall it doing that before.
Mike Blackwell
--
Sent via pgadmin-support mailin
Hello:
I installed PostgreSQL 8.3.7 (i386) on a CentOS 5.2. This is a fresh
install and there is no other server application installed on this
server except PostgreSQL.
Then I wanted to install "abAdmin" on this server. I wanted to install
"pgadmin3 v1.8.4" for "i386" machine but found out
On Tue, Apr 7, 2009 at 9:12 AM, Ashesh Vashi
wrote:
> Hi Regina,
>
> Thanks for reporting this.
> This is a bug.
>
> Dave,
> Please find the patch for it.
Thanks - patch applied.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgadmin-support mailing list (pgadmin-sup
Hi Regina,
Thanks for reporting this.
This is a bug.
Dave,
Please find the patch for it.
Paragon Corporation wrote:
This worked in pgAdmin III 1.8 and I believe it worked in 1.9 beta too.
When I try to create a batch job step with 1.10 beta 1, I get an error -
looking at the sql it looks lik
This worked in pgAdmin III 1.8 and I believe it worked in 1.9 beta too.
When I try to create a batch job step with 1.10 beta 1, I get an error -
looking at the sql it looks like its missing the last argument jstdbname
Creating SQL jobs seems to work fine though.
I tried against both a PostgreSQ
