Details
-
Bug
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Done
-
None
-
-
Thor
-
R3 2021 Bug Fix
-
Cornell
Description
Running in folio-snapshot, the LDP app allows selecting the "public" schema but not "folio_reporting" which contains the derived tables. I do not know if this involves ui-ldp or mod-ldp or both. I checked the permissions in the LDP database, and the "ldp" user appears to have access to the "folio_reporting" tables.
ldp=# \dn+ folio_reporting
List of schemas
Name | Owner | Access privileges | Description
-----------------+----------+----------------------+-------------
folio_reporting | ldpadmin | ldpadmin=UC/ldpadmin+|
| | ldp=UC/ldpadmin |
(1 row)
ldp=# \dp folio_reporting.holdings_ext
Access privileges
Schema | Name | Type | Access privileges | Column privileges | Policies
-----------------+--------------+-------+---------------------------+-------------------+----------
folio_reporting | holdings_ext | table | ldpadmin=arwdDxt/ldpadmin+| |
| | | ldp=r/ldpadmin | |
(1 row)
This was originally reported by Vandana Shah from Cornell:
Hi Nassib, one of the bugfest tests (Derived Table Test, #T933068) wants me to select 'folio_reporting' as a schema from the Schema drop-down menu in snapshot, but the only option I have is to select 'public'.