Re: enforce naming convention

From: "SunWuKung" <Balazs(dot)Klein(at)t-online(dot)hu>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: enforce naming convention
Date: 2006-04-17 14:26:24
Message-ID: 1145283984.736324.292180@t31g2000cwb.googlegroups.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I know that one of the main reasons why schemas are there is to make it
possible to use identical table names, but this time they want to use
it to separate tables purely because they feel they would find their
ways better that way. On the other hand I feel that this separation
will be somewhat arbitrary and may change in the future - to make sure
that tables will be freely movable between schemas I want to make sure
that there will be no identical names.

This may be totally wronb, but what about writing a Before Insert
trigger on the pg_catalog.pg_class table checking if there is already a
table with that name and if yes prevent the insert?
Is there something against doing so?

Thanks for the help.
SWK

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-04-17 14:42:25 Re: enforce naming convention
Previous Message Tom Lane 2006-04-17 14:18:51 Re: hard shutdown of system