Chris Reigrut wrote:
> Is there any way to distinguish between an empty string ('') and a
NULL
> string value in the query tool?
I'd like to resurrect this question from a while ago. It does not seem
like it got any response. It would be great if pgAdmin's Query Tool had
a setting similar to psql
This is sort of an enhancement idea: currently if you run pgAdmin III
its help files by default assume an 8.1 PG, which is a bit confusing,
because one could be (as I am) administering/connecting to some pre-8.1
servers through pgAdmin III. It would be quite nice if the help files
were either sensi
Is this a known problem? Is there a fix for it? It seems that pgAdmin
(v.1.4.1 for sure, but I think some prior versions as well) on Windows
corrupt the pgpass.conf file by deleting existing entries and adding
"garbage" ones. This is not a huge problem for pgAdmin itself, although
this presents its
> If you remove your file altogether and just let pgAdmin manage it
> itself, does it then corrupt it as well?
I tried that for a bit a while ago and I did not see any corruption, but
I am not sure my tests were exhaustive. The problem is that that is
really not a solution for me because I want to
> What else should I do to make it happen?
>
> If you look in your logs, you should see something like:
> May 17 13:24:49 fritz postgres[13852]: [3-1] LOG:
> autovacuum: processing database "postgres"
Not sure why this thread is on pgadmin-support (general would be a
better place for it), but d
this is somewhat minor: most windows applications seem to retain the
clipboard after the application is closed. pgadmin does not, which seems
non-standard. i have had a couple of "oops" moments and lost work
because of this. i have seen this on pgadmin III running on windows
1.4.1
george
A small but very annoying bug in pgAdmin 1.4.3 on Windows:
-- in the query select some text with the mouse;
-- now click somewhere on the selected text--as expected the selection
is lost--your cursor is somewhere in the middle of the previously
highlighted text;
-- now try to move your cursor
the behavior described by jl definitely happens to me too on a straight
out of the box, freshly installed windows xp sp2 with an american
english untweaked keyboard (this is about as stock as it gets--a brand
new computer, not much installed yet in terms of other software).
also as described by he
> > also as described by heiko selber the data edit
> > functionality seems to
> > be completely non-working.
>
> *Completely non-working*? You mean you cannot edit data and save it
> even if you don't hit the delete key? You cannot delete rows by
> selecting the row and using the delete key or
Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> George Pavlov
> Sent: Thursday, August 03, 2006 11:47 AM
> To: pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] pgAdmin 1.4.3 bug with delete
> button in win32 & OTHER
&g
PgAdmin III Query 1.6 Beta 2 is pretty unusable to me (WinXP SP2, stock
US install) -- it crashes fairly regularly upon query submission and I
end up losing a lot of my edits. FWIW, in 99% of the times I submit
queries by highlighting using keyboard + F5. No particular pattern of
usage causes this,
Dave,
It still crashes upon query submittal. I see no difference from beta2 in
this aspect.
George
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dave Page
> Sent: Friday, October 13, 2006 12:14 AM
> To: George Pavlov;
I had sent a version of this bug report to Dave Page directly a few days
ago, but let me clarify and do it through the forum. It seems that
pgAdmin 1.6 beta on windows suffers from some old password issues -- one
that is consistent, the other one I cannot reproduce reliably:
(a) the intermittent/n
pgAdmin v.1.6 beta 3 (5508:5517) has been good for me so far. all the issues i
had with previous versions seem fixed and i can't find new ones ;-) good job,
dave!
i am still a bit bummed about two of my biggest pgAdmin pet peeves not being
resolved (no distinction between a NULL and a zero-leng
> I grant you that I don't think the query grid does
> differentiate - I'll bung that on the roadmap.
i did mean the query grid (i hardly ever use the edit grid). i thought
it was on the roadmap:
http://archives.postgresql.org/pgadmin-support/2006-01/msg00013.php
> > and the loss of clipboard a
I think Dave fixed one of the cases that caused this a few revs ago, but
another one still remains. Steps to reproduce:
In pgAdmin 1.4.2:
* connect to a configured DB running on a networked machine
* open query
* issue a query
* observe result set
* disconnect your network connection (plug out a
Shouldn't it be fairly easy to make pgAdmin reconnect do servers it has
lost its connection to? After all it has all the connection information
(assuming password is saved) and could try to re-establish it?
I personally use a laptop and often switch connections (wired LANs,
wifi, cellular broadban
How is one (or is one) supposed to rename a DB through the pgAdmin UI?
In 1.4.2 in the DB properties dialog the OK button becomes enabled if
you changed the name in the dialog, but you get an error about renaming
the current DB (there does not seem to be a way to not have that DB be
your current DB
this might be a bug or me misunderstanding how things work (in which
case please help). in pgadmin 1.6.* selecting view/system objects
results in system objects (such as the information_schema and pg_catalog
schemas) showing in the tree view. i am guessing that for 1.8 the
equivalent functionality
19 matches
Mail list logo
