Re: Hiding table structure information
От
Aaron Bono
Тема
Re: Hiding table structure information
Дата
Msg-id
bf05e51c0606261748v6188d251qb515466b71e17d48@mail.gmail.com
Ответ на
Re: Hiding table structure information (Jonah H. Harris)
Список
Дерево обсуждения
Hiding table structure information "Carlos H. Reimer" <carlosreimer@terra.com.br>
RES: Hiding table structure information "Rodrigo Sakai" <rodrigo.sakai@zanthus.com.br>
RES: Hiding table structure information "Carlos H. Reimer" <carlosreimer@terra.com.br>
Re: RES: Hiding table structure information Tom Lane <tgl@sss.pgh.pa.us>
Re: Hiding table structure information "Jonah H. Harris" <jonah.harris@gmail.com>
Re: Hiding table structure information "Aaron Bono" <postgresql@aranya.com>
Re: Hiding table structure information Bruno Wolff III <bruno@wolff.to>
Re: Hiding table structure information "Aaron Bono" <postgresql@aranya.com>
Re: Hiding table structure information Jim Nasby <jnasby@pervasive.com>
Would there be a way to set up the 2 databases - one with the tables and data and the other that connects to the first with views into the second database?
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
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@gmail.com> wrote:
On 6/26/06, Carlos H. Reimer <carlosreimer@terra.com.br> 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@enterprisedb.com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/
В списке pgsql-admin по дате отправления
