| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | Oliver Brück <oliver(dot)brueck(at)waagner-biro(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: No triggers visible for different user in information_schema.triggers |
| Date: | 2005-02-18 11:00:52 |
| Message-ID: | 200502181200.53606.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Am Donnerstag, 17. Februar 2005 18:43 schrieb Michael Fuhr:
> SQL:2003 (Working Draft) says:
>
> Identify the triggers on tables in this catalog that are accessible
> to a given user or role.
>
> Apparently PostgreSQL implements the SQL:1999 specification of
> information_schema.triggers.
While that is true, superuserdom consistently does not play any role in the
information schema for the purpose of figuring out what is accessible to a
certain user. This may be considered a bug, but it would also create
inconsistencies because the state "accessible to" is defined by other
information schema tables where superuserdom cannot be represented.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Fradkin | 2005-02-18 14:59:26 | trrouble inserting stuff like é |
| Previous Message | CoL | 2005-02-18 08:26:26 | Re: VIEW / ORDER BY + UNION |