Dave Page wrote:
Connecting:
When connecting to a database as non-superuser, it shows the
message: An error has occured:
ERROR: pg_shadow: permissin denied
I don't think this is really an error. It is expected
behaviour, but the
current message might confude people. Maybe it should say
something like
"Insufficient permissions to enumerate users.", but it would
be really
neat if the users entry in the left pane just greyed out and
the message
only appeared when somebody clicks on it.
I quite agree with this one, however it's a bit tricky (to do properly)
with PostgreSQL 7.3 as the message will change for localised versions,
so it's difficult to reliably detect what went wrong.
When 7.4 is at a usable state we will have a better way of doing this as
it will include error codes, alternatively we could hack it by only
enumerating users for superusers, or those with select permissions on
pg_shadow.
I changed the schema code to use pg_user wherever possible, and checking
for access privilege to pg_shadow to try to resolve the encrypted password.
Vacuum:
It would be nice if vacuum had the option to do a verbose
vacuum and the
result was displayed in screen. Also, a separate button for analyze
would be nice.
Agreed (and added to todo).
View data:
I really like the inline editing of data in tables. Much better then
what it was. However, horizontal and vertical scrollbars only appear
when I maximize the window.
Yes, we've seen this error before. A simple resize normally makes the
scrollbars appear. Andreas: did you get a chance to look at this at all?
Can we just switch the scrollbars on permanently? 99% of the time they
would probably be there anyway...
Nasty wx... There already was some code for non-win32, and I activated
it for win32 now. wxWindows will optimize away the scrollbars if not
initially necessary, and they will never come back... Now the window is
forced extra-small so that scrollbars are necessary right from the start.
When are you going to release an official alfa/beta version?
I was hoping we could aim to coincide with the release/beta for
PostgreSQL 7.4, but that might be a bit ambitious.
This pessimism is illegal ;-), we should go ahead to match that goal.
Regards,
Andreas
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
