SEO

Hello Dave,

I was using that .exe from yesterday intensly.

There was only one "stuck" situation, and that was a long running query, and
in the middle of the process a virus scanner started to scan. So far from my
side: good bugfixing!


One very frustrating habbit was the resizing of the columns of the data
grid: I could drag them to every width; but with the next run of the query
they moved back to standard. I am not sure if this qualifies as "bug", or
rather "feature request", as "do not resize column-width unless types or
numbers of query result columns change"

Thansk for all that good work,

Harald


--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstraße 202b
70197 Stuttgart
0173/9409607
-
Python: the only language with more web frameworks than keywords.

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-length string in the grids and the loss of clipboard after closing the app), but we will wait patiently!


> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailtogadmin-support-owner@postgresql.org] On Behalf Of
> Harald Armin Massa
> Sent: Tuesday, October 24, 2006 12:13 AM
> To: Dave Page; pgAdmin Support
> Subject: [pgadmin-support] pgAdmin preBeta4 - results
>
> Hello Dave,
>
> I was using that .exe from yesterday intensly.
>
> There was only one "stuck" situation, and that was a long
> running query, and in the middle of the process a virus
> scanner started to scan. So far from my side: good bugfixing!
>
>
> One very frustrating habbit was the resizing of the columns
> of the data grid: I could drag them to every width; but with
> the next run of the query they moved back to standard. I am
> not sure if this qualifies as "bug", or rather "feature
> request", as "do not resize column-width unless types or
> numbers of query result columns change"
>
> Thansk for all that good work,
>
> Harald
>
>
> --
> GHUM Harald Massa
> persuadere et programmare
> Harald Armin Massa
> Reinsburgstraße 202b
> 70197 Stuttgart
> 0173/9409607
> -
> Python: the only language with more web frameworks than keywords.
>

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

On 25/10/06 17:46, "George Pavlov" <gpavlov@mynewplace.com> wrote:

> 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!

Thanks - and thanks for the feedback!

> 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-length string in the grids

Err, the edit grid has always distinguished between them - from
http://www.pgadmin.org/docs/dev/editgrid.html:

If an SQL NULL is to be written to the table, simply leave the field empty.
If you store a new row, this will let the server fill in the default value
for that column. If you store a change to an existing row, the value NULL
will explicitly be written.

And

If you want pgAdmin III to write an empty string to the table, you enter the
special string '' (two single quotes) in the field. If you want to write a
string containing solely two single quotes to the table, you need to escape
these quotes, by typing \'\'

The grid displays blank for null or '' for empty string, just as you would
enter. I grant you that I don't think the query grid does differentiate -
I'll bung that on the roadmap.

> and the loss of clipboard after closing the app), but we will wait patiently!

I didn't realise it did lose it. I'll add that too.

Regards, Dave


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

> 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/pgadm...1/msg00013.php

> > and the loss of clipboard after closing the app), but we
> will wait patiently!
>
> I didn't realise it did lose it. I'll add that too.

http://archives.postgresql.org/pgadm...5/msg00065.php

where is this "roadmap" anyway? might be good to review for my own
edification and to adjust expectations.

thanks!

george

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

On 25/10/06 19:45, "George Pavlov" <gpavlov@mynewplace.com> wrote:

>> 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/pgadm...1/msg00013.php
>

A similar item was on the Bugs list for the Edit Grid, and got removed when
I revised it this morning (because I did the work a while back):

- [Edit grid] bool editing doesn't know NULL; major redesign needed

It turned out not to be quite so major :-)

>>> and the loss of clipboard after closing the app), but we
>> will wait patiently!
>>
>> I didn't realise it did lose it. I'll add that too.
>
> http://archives.postgresql.org/pgadm...5/msg00065.php

Must have missed that.

> where is this "roadmap" anyway? might be good to review for my own
> edification and to adjust expectations.

I only wrote it at lunchtime actually - it's the list of items that we
actually expect to do in the next release cycle (as opposed to the TODO list
which contains all sorts of idea that may never get done):

http://www.pgadmin.org/development/roadmap.php

Regards, Dave.


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

> If you want pgAdmin III to write an empty string to
> the table, you enter the
> special string '' (two single quotes) in the field.
> If you want to write a
> string containing solely two single quotes to the
> table, you need to escape
> these quotes, by typing \'\'

I think the simplest choice is to use a Enterprise
Manager approach: CTRL + 0 (zero) is NULL, typing ''
is "strange"

Best regards,
Mauro

__________________________________________________
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi
http://mail.yahoo.it

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

> -----Original Message-----
> From: Mauro Bertoli [mailto:bertolima@yahoo.it]
> Sent: 26 October 2006 09:54
> To: George Pavlov; Dave Page; pgAdmin Support
> Subject: Re: [pgadmin-support] pgAdmin preBeta4 - results
>
> > If you want pgAdmin III to write an empty string to
> > the table, you enter the
> > special string '' (two single quotes) in the field.
> > If you want to write a
> > string containing solely two single quotes to the
> > table, you need to escape
> > these quotes, by typing \'\'
>
> I think the simplest choice is to use a Enterprise
> Manager approach: CTRL + 0 (zero) is NULL, typing ''
> is "strange"

It's been that way since the beginning - I don't think it's going to
change now.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match