#40173 [Opn->Fbk]: pg_metadata ignores visibility scope of current postgres user
| From: | tony2001@php.net | Date: | Fri, 19 Jan 2007 17:04:01 +0000 |
| Subject: | #40173 [Opn->Fbk]: pg_metadata ignores visibility scope of current postgres user | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-107779@lists.php.net to get a copy of this message | ||
ID: 40173
Updated by: tony2001@php.net
Reported By: denis at edistar dot com
-Status: Open
+Status: Feedback
Bug Type: PostgreSQL related
Operating System: Linux kernel 2.6.17
PHP Version: 5.2.0
New Comment:
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.
A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external
resources such as databases, etc. If the script requires a
database to demonstrate the issue, please make sure it creates
all necessary tables, stored procedures etc.
Please avoid embedding huge scripts into the report.
Previous Comments:
------------------------------------------------------------------------
[2007-01-19 16:54:41] denis at edistar dot com
Description:
------------
pg_metadata does not check if the current postgres user has the correct
rights on the visibility of the table passed as parameter.
So, if we have two postgres users (userA and userB for example) with
two authorization schemas (that have the same name userA and userB) and
in each schema we have a table with the same name but with different
definition,
we can access only one of the two tables...
Also pg_metadata does not accept passing the table with a namespace
attached (for exampl userA.mytable)
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=40173&edit=1