Originally posted by Martin Doering
> >Do *not* use public synonyms. Create private ones as
> needed.
>
> Yes, I know. But this gets complicated, if I want many (>50) Users let
> make use of my objects. Then I would have to create private synonym
> for each of them. It would be helpful, if one could put synonyms in
> something like a role, like it is done with the grants.
>
An alternative that requires no synonyms at all is ALTER SESSION SET
CURRENT_SCHEMA=XXX;
Originally posted by Martin Doering
> But it is interesting, that many people use such conventions. For
> example, we have some tables and some sequences related to them. So
> here I think it makes sense to give them both the same names, but let
> the sequence start (or end) with an addition.
>
Naming table-related objects in a way that clearly links them to the
table is helpful; and the easiest way to do that is with prefixes or
suffixes like "SEQ_", "_PK" etc. But giving the tables themselves a
prefix like "T_" or the disgusting VB-like names such as "tblEmployee"
is totally unhelpful and extremely irritating. IMHO.
--
Posted via http://dbforums.com
Received on Wed Jul 02 2003 - 05:15:03 CDT
