Actually I am interested because I will soon need to set up a way to feed data to multiple databases and would love to have a stored procedure or trigger that, when the data is updated in one database, the changes are propagated to all the other databases.
Thanks,
Aaron
On 6/26/06, Jonah H. Harris <jonah.harris@xxxxxxxxx> wrote:
On 6/26/06, Carlos H. Reimer <carlosreimer@xxxxxxxxxxxx> wrote:
> Maybe the question should be reformulted to: is there a way to hide
> pg_catalog schema? I think it can?t not be done because all metadata are
> there, but maybe somebody can see a solution.
You could use a set returning function and a view to hide the original
table's details. As for hiding pg_catalog... I believe you could
create a rule on it.
Never tried to hide something this extensively... and don't really
understand a practical reason for doing so. Remember, security
through obscurity is flawed from the get go.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 2nd Floor | jharris@xxxxxxxxxxxxxxxx
Iselin, New Jersey 08830 | http://www.enterprisedb.com/
