Hi,
Le 20/01/2010 19:38, legio nostra a écrit :
> [...]
> I have a database created with the program pgadmin3. The geo-referencing
> system is the Datum 73 / Modified Portuguese
>
> Grid (deprecated) "EPSG: 27492" and wanted to change the whole database to
> the coordinate system ETRS89 / Portuga
Hello everyone,
I have a database created with the program pgadmin3. The geo-referencing
system is the Datum 73 / Modified Portuguese
Grid (deprecated) "EPSG: 27492" and wanted to change the whole database to
the coordinate system ETRS89 / Portugal TM06 (EPSG: 3763).
How can I make this transfor
I don't think the assumption that CREATE implies SELECT is a good one. It is
probably true in most cases, but there might be folks that have set it up
otherwise.
It seems that the Dependents tab on a role under the Login Roles might be
the place to look for tables, etc, that the login has access t
When I say end-user I am thinking from a Data Warehouse perspective
where there are many SELECT-only users. For them, their experience is
frustrating and confusing when they need to go through many schemas and
tables that they don't care about to find what they can access. That is
why I sugge
Thank for your answer.
There are advantages / disavantages for end-users with the 2 solutions
Solution 1:
Let the end-user see only the schemas/tables he is allowed to use (as Oracle
SQL Developper does, for example) :
+ : easy to retrieve their data without been lost if the database
has
On Tue, Jan 19, 2010 at 8:57 PM, Joe Garrett wrote:
> I hearby place my vote for allowing us to hide schemas and tables that a
> user has no priviliges on (and columns too would be useful but of secondary
> importance). I believe this is a PostgreSQL request and not a pgAdmin3
> request. I regul
