Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Major |
| Complexity | Unknown |
| Component | App - Visual Editing |
| Version | 13.0 |
Version: 13.0.1-2
Build #: 32256
Build Date: 2013-May-07 01:07:30 PM
Table Permissions are not displayed similar to pgAdmin III
To reproduce:
1. Open ADS and create 2 Server Registrations to PostgreSQL with usernames - postgres and sys. Password is our standard password and
the host is 10.168.11.56
2. Now connect as postgres and navigate to the postgres database and take Table Properties of public.table01. Go to the Permissions tab and
in the Drop down for Permissions for Grantee Type - select Groups. You can see Privileges
3. Now connect as sys and navigate to the same table and in the permissions tab for Groups, no Privileges are visible.
4. Now open pgAdmin III and connect as sys and you can see that permissions are displayed correctly. See screenshot
There are difference in the way AD Studio 13.0 displays permissions from pgAdmin III
The sql to create the tests is attached with the screenshots
|
818 B
|
|
91 KB
|
|
77 KB
we use a catalog table called pg_authid and the new id does not have permissions to this table. Will look to see if we can extract permissions using the tables pgadmin.
Will change privileges extraction for tables & views to use the information_schema privileges tables. We will still use the pg_authid table to extract other privileges as the information schema does not hold all of the needed extraction information though they seem to be pushing towards improving these tables as time goes on. Perhaps in the future we can discontinue the need for pg_authid. pg_admin also uses pg_authid for certain privileges extraction and without permissions to this system catalog table will be unable to display proper priv information.
Need to discuss this further as the information schema views seem to have missing data depending on logged in account.
Will change privileges extraction for tables & views to use the information_schema privileges tables. We will still use the pg_authid table to extract other privileges as the information schema does not hold all of the needed extraction information though they seem to be pushing towards improving these tables as time goes on. Perhaps in the future we can discontinue the need for pg_authid. pg_admin also uses pg_authid for certain privileges extraction and without permissions to this system catalog table will be unable to display proper priv information.
Need to discuss this further as the information schema views seem to have missing data depending on logged in account.
After some carful considerations we will not use information_schema views. Modified the extraction so we do not use pg_authid anymore. issue will be fixed for 13 and above of datastudio. This affects only postgreSQL 8.1 and above
fixed
After some carful considerations we will not use information_schema views. Modified the extraction so we do not use pg_authid anymore. issue will be fixed for 13 and above of datastudio. This affects only postgreSQL 8.1 and above
fixed
Issue #9060 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 13.0.1-13 |
| No time estimate |
we use a catalog table called pg_authid and the new id does not have permissions to this table. Will look to see if we can extract permissions using the tables pgadmin.