Hi,
I am using PgAdminIII 1.6.3 on windows xp, I changed the font size in the
preferences dialog box to be size 12 when I restarted PgAdmin and went to
preferences dialog box I could not see the change font button because it was
beyond the right edge of the window. I was unable to resize the prefe
Here's another, quicker way to do it.
SELECT column1,
column2,
COALESCE(maybe_null_column, 'NULL')
FROM your_table;
Note: If maybe_null_column is not a character data type,
then you need to coerce it. ie: maybe_null_column::text
---(end of broadcast
You can do that now with a little code as follows:
SELECT column1,
column2,
CASE WHEN maybe_null_column IS NULL THEN 'NULL' ELSE
maybe_null_column END
FROM your_table;
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ketema Harris
Sent: Thu
I was wondering if were possible in a future release of pgadmin, to
display 'null' in all query result panes where its an actual null
value instead of just a blank, because it is indistinguishable from
an empty string at this time.
Thanks.
---(end of broadcast)-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear all,
I've just uploaded a build of pgAdmin3 1.6.3 for debian/etch on the
amd64 architecture. Sebastian P. Luque (CCed) provided this build today.
As usual PostgreSQL mirrors should sync during the next hours/days.
Thanks for your time Sebastian
Guillaume Lelarge wrote:
> Dave Page a écrit :
>> Guillaume Lelarge wrote:
>>> I didn't change the CHANGELOG file. Should I edit it for such small
>>> commits ?
>> Nah, I wouldn't bother.
>>
>
> Sorry, I did it this morning with the "Sort servers' list
> alphabetically." patch. I'll delete it on m
Guillaume Lelarge wrote:
> Dave Page a écrit :
>> [...]
>> BTW; did you fix that SQL formatting error that Erwin reported?
>>
>
> Here is the patch that fixes it.
Please feel free to commit trivial fixes such as this without asking
first - we can always rollback or fix if a problem is found later
Laurent ROCHE wrote:
> Hi,
>
> Another feature request:
> I would like to be able to rename a database by right clicking on a database
> and choosing Rename from the context menu (which does not exist right now).
>
> I know I can do the same thing by opening a query window and writing a ALTER
>
In Windows Vista, backup and restore in pgAdmin is not working.
Task Manager shows pg_dump or pg_restore processes but they have never
finished.
I turned UAC off, selected Run as administrator and run in XP SP2
compatibility mode but problem persist.
Running same commands from bat file works
I'm using pgAdminIII 1.6.3 on a windows machine, and the program reliably
dies whenever I try pasting 64K of text into a TEXT column using the table
editor.
The text column is defined as 65000 in length, and the db is using
SQL_ASCII.
It happens every time.
Please fix this most annoying issue.
Laurent ROCHE a écrit :
> Another feature request:
> I would like to be able to rename a database by right clicking on a database
> and choosing Rename from the context menu (which does not exist right now).
>
> I know I can do the same thing by opening a query window and writing a ALTER
> DATAB
Dave Page a écrit :
> Guillaume Lelarge wrote:
>> I didn't change the CHANGELOG file. Should I edit it for such small
>> commits ?
>
> Nah, I wouldn't bother.
>
Sorry, I did it this morning with the "Sort servers' list
alphabetically." patch. I'll delete it on my next commit.
--
Guillaume.
Dave Page a écrit :
> [...]
> BTW; did you fix that SQL formatting error that Erwin reported?
>
Here is the patch that fixes it.
Regards.
--
Guillaume.
Index: pgadmin/schema/pgTable.cpp
===
--- pgadmin/schema/pgTable.cpp (révis
Hi,
Another feature request:
I would like to be able to rename a database by right clicking on a database
and choosing Rename from the context menu (which does not exist right now).
I know I can do the same thing by opening a query window and writing a ALTER
DATABASE ... RENAME TO ...
command,
- Message d'origine
De : Bob <[EMAIL PROTECTED]>
À : pgadmin-support@postgresql.org
Envoyé le : Jeudi, 24 Mai 2007, 2h52mn 23s
Objet : [pgadmin-support] Improvement to Dropped DB Connections
In other words --- EVEN IF the DB connection is closed by accident,
pgAdmin should not requi
Guillaume Lelarge wrote:
> Dave Page a écrit :
>> Guillaume Lelarge wrote:
>>> Dave Page a écrit :
Guillaume Lelarge wrote:
> I can take care of this :
> - update the button's title ;
> - grow the Replace button.
> Dave, do you agree on this ?
Sure, go ahead.
>
Hello,
I have problems with dropped database connection, as described in the
online FAQ (below).
While the explanation is interesting, it's not really up to snuff for
most of us. I don't know how to set up an SSH tunnel, nor should I have
to just to get pgAdmin working. It would be nice if pgAd
Hi,
(While talking of connection names, see other post "Edit Data windows title")
I just realised the connection name was not used at all in the Query window.
That's more than a shame because if I want to use another connection, a little
window pops up and offer to change database with a dropdow
Of course the port number is essential BUT at the moment the Edit Data windows
title is of the form:
MyServerName (HostRef:PortNumb) - dbName - tableName
(note that I changed the notation from my previous post to try and be clearer)
However the point (to me) of giving a name to a connection (MySe
19 matches
Mail list logo
