Re: Schema Design.

From: Preston <dontwantany_at_nowhere.invalid>
Date: Thu, 9 Dec 2010 11:17:40 +0000 (UTC)
Message-ID: <idqdsk$bqh$1_at_news.eternal-september.org>



HoneyMonster wrote:

> On Thu, 09 Dec 2010 10:28:01 +0000, Preston wrote:
>
> >
> > A separate schema for each app is one option, but who gets the
> > tables/procs used by multiple apps? We could use a "SHARED" schema
> > for those, but I suspect that would get messy as people develop
> > app-specific objects in the future then realise they could be used
> > by other apps too & move them to "SHARED". Either option could be a
> > nightmare when it comes to remembering to put schema. in front of
> > the object names, not to mention the potential re-work needed if
> > objects are moved to different schemas.
> >
> > Thoughts anyone?
>
> Don't hard code schema names in application code; use synonyms.

Sure, & that's what we do. That's only one aspect though.

-- 
Preston.
Received on Thu Dec 09 2010 - 05:17:40 CST

Original text of this message