|
Home > Archive > Pgadmin > November 2005 > Hide databases
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Uwe Dalluege 2005-10-27, 8:23 pm |
| Hi,
is it possible to hide the databases where I am not the owner?
In our university we have many postgresql user.
Each user has his own database.
When I start pgAdmin all databases are displayed.
Is there a button to avoid showing these databases?
Best regards,
Uwe Dalluege
--------------------------------------------------------------------------
Hochschule fuer Angewandte Wissenschaften Hamburg
- University of Applied Sciences -
Fachbereich Geomatik
Rechenzentrum
Dipl.-Ing. Uwe Dalluege :-)
Hebebrandstr. 1
22297 Hamburg
Tel.: +49 40 42875 - 5335 oder 5353 oder 5313
Fax: +49 40 42875 - 5409
E-Mail: mailto:uwe.dalluege@rzcn.haw-hamburg.de
Url: http://www.haw-hamburg.de/geomatik/
--------------------------------------------------------------------------
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
| |
| Andreas Pflug 2005-10-27, 8:23 pm |
| Uwe Dalluege wrote:
>Hi,
>
>is it possible to hide the databases where I am not the owner?
>
>
No, not currently.
Regards,
Andreas
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
| |
| Andreas Pflug 2005-10-31, 8:24 pm |
| Uwe Dalluege wrote:
> Hi,
>
> is it possible to hide the databases where I am not the owner?
>
> In our university we have many postgresql user.
> Each user has his own database.
> When I start pgAdmin all databases are displayed.
> Is there a button to avoid showing these databases?
Ok,
Dave and me have been discussing a little about this request, and we'll
probably implement a configurable SQL restriction for that in 1.5/1.6.
Your requirement seems typical for universities, let's declare this as
my contribution to the Deutsches Bildungssystem!
Greetings to the Geomatikum, where I spent quite some sleepy mornings in
lectures, I remember...
Regards,
Andreas
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
| |
| Uwe Dalluege 2005-11-01, 7:23 am |
| Andreas and Dave,
thank you very much for your intent
to implement a configurable SQL restriction.
I think, the "Deutsche Bildungswesen"
would be delighted! :-) (and so I)
We have about 300 students working with
PostgreSQL so you can imagine the little confusion
seeing 300 databases.
We tried to use ONE database with 300 schemata
(one student, one schema)
but this was the same problem :-(
Best regards,
Uwe
Andreas Pflug wrote:
[color=darkred]
> Ok,
> Dave and me have been discussing a little about this request, and we'll
> probably implement a configurable SQL restriction for that in 1.5/1.6.
> Your requirement seems typical for universities, let's declare this as
> my contribution to the Deutsches Bildungssystem!
>
> Greetings to the Geomatikum, where I spent quite some sleepy mornings in
> lectures, I remember...
>
> Regards,
> Andreas
>
> Uwe Dalluege wrote:
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
| |
| Andreas Pflug 2005-11-01, 8:48 pm |
| Uwe Dalluege wrote:
> Andreas and Dave,
>
> thank you very much for your intent
> to implement a configurable SQL restriction.
> I think, the "Deutsche Bildungswesen"
> would be delighted! :-) (and so I)
>
> We have about 300 students working with
> PostgreSQL so you can imagine the little confusion
> seeing 300 databases.
>
> We tried to use ONE database with 300 schemata
> (one student, one schema)
> but this was the same problem :-(
It's on the TODO list now; I'll try to implement it as soon as V1.4 is out.
Regards,
Andreas
---------------------------(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
|
|
|
|
|