Here's an easier one:
I'd like a menu item to save all open query windows. Currently if I
have 10 or 11 windows open, I have to go through, saving them one at a time.
--Josh Berkus
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
h
Folks,
I often use pgAdmin for demos and training. For that purpose, as well
as for odd screen sizes, it would be really useful to have some control
over the text size in the query result grid. Currently, I can make the
query text size any point size I like, but the results are always the same.
On Wed, Feb 24, 2010 at 2:50 PM, Andreas Laggner
wrote:
> Hi List,
>
> i want to execute my sql-files, written with pgadmin 1.10.0 (from
> binaries for openSuse 11.2 64bit) directly on the server via nohup. But
> since 1.10 (i never had that problem in 1.08) the sql-file saved by
> pgadmin begins
Hi List,
i want to execute my sql-files, written with pgadmin 1.10.0 (from
binaries for openSuse 11.2 64bit) directly on the server via nohup. But
since 1.10 (i never had that problem in 1.08) the sql-file saved by
pgadmin begins with 3 control characters. I can only see these
characters, if i ope
Hi List,
i'm running 1.10.0 binary with openSuse 11.2 64bit. When i open a
sql-query the window size is standard and not as i left it last time i
used pgadmin3. How can i get pgadmin3 remembering the window size? Hint:
this problem occurs on more 11.2 machines, but on the 11.1 ones pgadmin
remembe
It would be very useful to be able to export the results of a query as
select into statements, at least in the case when there is only one table in
the from clause.
If I create function with 2 or more default parameters in pgAdmin 1.10.1 for
windows, then after the command "Create Script" in function's tree I see
incorrect definition of function - default value is displayed only for every
second parameter.
How can I fix It?
Thanks
